This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build

From: Andi Kleen <ak at suse dot de>
To: Daniel Jacobowitz <dan at debian dot org>
Cc: weigand at i1 dot informatik dot uni-erlangen dot de, gcc at gcc dot gnu dot org,linux-kernel at vger dot kernel dot org, schwidefsky at de dot ibm dot com
Date: Thu, 1 Apr 2004 22:46:04 +0200
Subject: Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build
References: <200404011928.VAA23657@faui1d.informatik.uni-erlangen.de><20040401220957.5f4f9ad2.ak@suse.de><20040401203923.GA32177@nevyn.them.org>

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

Follow-Ups:
- Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build
  - From: Ulrich Weigand

References:
- Linux 2.6 nanosecond time stamp weirdness breaks GCC build
  - From: Ulrich Weigand
- Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build
  - From: Andi Kleen
- Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]