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
Date: Thu, 1 Apr 2004 22:46:04 +0200 [thread overview]
Message-ID: <20040401224604.5c3b45ff.ak@suse.de> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2004-04-01 20:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 19:28 Linux 2.6 nanosecond time stamp weirdness breaks GCC build Ulrich Weigand
2004-04-01 20:09 ` Andi Kleen
2004-04-01 20:39 ` Daniel Jacobowitz
2004-04-01 20:46 ` Andi Kleen [this message]
2004-04-01 21:01 ` Ulrich Weigand
2004-04-01 21:44 ` Andi Kleen
2004-04-01 22:39 ` Joe Buck
2004-04-01 22:44 ` Paul Jarc
2004-04-01 22:48 ` Ulrich Weigand
2004-04-01 23:58 ` Joe Buck
2004-04-02 0:13 ` Daniel Jacobowitz
2004-04-02 0:02 ` Jamie Lokier
2004-04-02 0:35 ` Paul Eggert
2004-04-02 1:14 ` Jamie Lokier
2004-04-02 7:57 ` James H. Cloos Jr.
2004-04-02 9:22 ` Paul Eggert
2004-04-02 16:23 ` Jamie Lokier
2004-04-02 20:45 ` Paul Eggert
2004-04-02 21:07 ` Jamie Lokier
2004-04-02 21:56 ` Paul Eggert
2004-04-03 4:59 ` Andrew Pimlott
2004-04-02 0:37 ` Andrew Morton
2004-06-07 16:03 ` Jörn Engel
2004-04-01 21:13 ` Janis Johnson
2004-04-01 21:41 ` Ulrich Weigand
2004-04-02 0:30 ` Alan Modra
2004-04-02 9:05 ` P
2004-04-02 17:27 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 20:51 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040401224604.5c3b45ff.ak@suse.de \
--to=ak@suse.de \
--cc=dan@debian.org \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=weigand@i1.informatik.uni-erlangen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.