From: Mark Mitchell <mark@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Andreas Tobler <andreast-list@fgznet.ch>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: Patch: automatic dependencies for gcc
Date: Thu, 27 Mar 2008 18:34:00 -0000 [thread overview]
Message-ID: <47EBE02A.9050103@codesourcery.com> (raw)
In-Reply-To: <m3k5jodv36.fsf@fleche.redhat.com>
Tom Tromey wrote:
> Richard> Well, as this only affects re-builds (?) in gcc/ it isn't
> Richard> fatal (I just hit Ctrl-C and make again, that makes it work).
>
> That seems very unsatisfying to me, especially because I can easily
> reproduce the problem with 'make -j2 all'.
>
> I think unpredictable hangs are much worse than manually maintaining
> dependencies. We can always try again in a couple years, after a new
> make is released.
>
> I'm bootstrapping the reversion on a couple machines now. I will send
> it before the end of the day.
Unfortunately, I agree that this is the right thing to do. I was really
excited about automated dependencies, but if automated parallel builds
don't work, we've got a large problem. Unless we can work around the
GNU make bug, or unless there's an available GNU make release that fixes
the problem, I think we have to back off.
Thank you for your efforts in this area!
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2008-03-27 17:58 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 21:15 Tom Tromey
2008-03-07 23:20 ` Joseph S. Myers
2008-03-07 23:28 ` Tom Tromey
2008-03-08 0:37 ` Ralf Wildenhues
2008-03-08 0:42 ` Tom Tromey
2008-03-08 14:33 ` Ralf Wildenhues
2008-03-08 16:20 ` Tom Tromey
2008-03-08 16:36 ` Ralf Wildenhues
2008-03-08 18:41 ` Ralf Wildenhues
2008-03-08 19:42 ` Tom Tromey
2008-03-09 14:40 ` Ralf Wildenhues
2008-03-09 15:07 ` Ralf Wildenhues
2008-03-09 16:02 ` Tom Tromey
2008-03-09 16:36 ` Ralf Wildenhues
2008-03-09 16:55 ` Tom Tromey
2008-03-11 0:01 ` Ben Elliston
2008-03-11 0:11 ` Tom Tromey
2008-03-18 14:35 ` Paolo Bonzini
2008-03-21 13:43 ` Tom Tromey
2008-03-21 17:43 ` Paolo Bonzini
2008-03-24 20:34 ` Tom Tromey
2008-03-25 8:33 ` Tom Tromey
2008-03-25 8:42 ` Paolo Bonzini
2008-03-25 15:43 ` Tom Tromey
2008-03-25 16:32 ` Paolo Bonzini
2008-03-25 17:27 ` Tom Tromey
2008-03-25 17:28 ` Tom Tromey
2008-03-25 17:29 ` Paolo Bonzini
2008-03-25 17:39 ` Tom Tromey
2008-03-25 18:00 ` Tom Tromey
2008-03-25 20:41 ` Ralf Wildenhues
2008-03-25 20:51 ` Tom Tromey
2008-03-25 21:03 ` Ralf Wildenhues
2008-03-26 2:08 ` Tom Tromey
2008-03-25 22:26 ` Andreas Tobler
2008-03-26 3:26 ` Tom Tromey
2008-03-26 13:16 ` Richard Guenther
2008-03-26 13:17 ` Tom Tromey
2008-03-26 13:21 ` Richard Guenther
2008-03-26 13:53 ` Tom Tromey
2008-03-26 15:05 ` Basile STARYNKEVITCH
2008-03-26 15:27 ` Tom Tromey
2008-03-26 16:47 ` Basile STARYNKEVITCH
2008-03-27 12:02 ` Richard Guenther
2008-03-27 15:45 ` Tom Tromey
2008-03-27 16:40 ` Tom Tromey
2008-03-27 17:14 ` Richard Guenther
2008-03-27 17:41 ` Tom Tromey
2008-03-27 18:34 ` Mark Mitchell [this message]
2008-03-27 19:39 ` Tom Tromey
2008-03-27 19:45 ` Diego Novillo
2008-03-27 20:07 ` Tom Tromey
2008-03-27 20:16 ` Diego Novillo
2008-03-27 20:31 ` Paolo Bonzini
2008-03-27 20:20 ` David Daney
2008-03-27 21:42 ` Tom Tromey
2008-03-27 22:43 ` Ralf Wildenhues
2008-03-27 22:47 ` Tom Tromey
2008-03-27 19:21 ` Paolo Bonzini
2008-03-25 21:00 ` Tom Tromey
2008-03-25 21:07 ` Ralf Wildenhues
2008-03-25 21:44 ` Tom Tromey
2008-03-20 16:54 ` Tom Tromey
2008-03-27 16:41 Dominique Dhumieres
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=47EBE02A.9050103@codesourcery.com \
--to=mark@codesourcery.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=andreast-list@fgznet.ch \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=tromey@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).