Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 25 Jul 2001 19:18:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 25 Jul 2001 19:18:40 -0400 Received: from neon-gw.transmeta.com ([209.10.217.66]:51721 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Wed, 25 Jul 2001 19:18:33 -0400 Date: Wed, 25 Jul 2001 16:16:32 -0700 (PDT) From: Linus Torvalds To: Andrea Arcangeli cc: Richard Gooch , Chris Friesen , Jeff Dike , user-mode-linux-user , linux-kernel , Jan Hubicka Subject: Re: user-mode port 0.44-2.4.7 In-Reply-To: <20010726004957.F32148@athlon.random> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Original-Recipient: rfc822;linux-kernel-outgoing On Thu, 26 Jul 2001, Andrea Arcangeli wrote: > > I will if Honza assures me that no future version of gcc will cause me to > crash if I don't declare xtime volatile and I play with it while it can > change under me (which seems not the case from his last email). WHY DO YOU NOT ADD THE "VOLATILE" TO THE PLACES THAT _CARE_? This is not a gcc issue. Even if gcc _were_ to generate bad code, the global volatile _still_ wouldn't be the correct answer. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/