Date: Thu, 1 Apr 2004 22:46:04 +0200
From: Andi Kleen <ak@suse.de>
To: Daniel Jacobowitz <dan@debian.org>
Cc: weigand@i1.informatik.uni-erlangen.de, gcc@gcc.gnu.org,
       linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com
Subject: Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build
Message-Id: <20040401224604.5c3b45ff.ak@suse.de>
In-Reply-To: <20040401203923.GA32177@nevyn.them.org>
References: <200404011928.VAA23657@faui1d.informatik.uni-erlangen.de>
	<20040401220957.5f4f9ad2.ak@suse.de>
	<20040401203923.GA32177@nevyn.them.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 766
Lines: 18

On Thu, 1 Apr 2004 15:39:23 -0500
Daniel Jacobowitz <dan@debian.org> wrote:
> > 
> 
> (I haven't tested anything but...) why should this fix it?  Ulrich's
> problem happens when the .o file is flushed from the cache, and then
> stat'd; it now appears to be older than the .c file.  With a change to
> round up instead, if the .c file is flushed from the cache before the
> .o, the .c will still suddenly appear to be newer than the .o.

That is what he wants I think. It's logically just like taking a bit longer. 

-Andi
-
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/