public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kelley Cook <kcook@gcc.gnu.org>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Steven Bosscher <stevenb@suse.de>,
	membar@gcc.gnu.org, gcc@gcc.gnu.org, neroden@twcny.rr.com
Subject: Re: Parallel make also broken now...
Date: Tue, 07 Sep 2004 18:16:00 -0000	[thread overview]
Message-ID: <413DFB10.8070009@gcc.gnu.org> (raw)
In-Reply-To: <8363278.1094495761568.SLOX.WebMail.wwwrun@extimap.suse.de>

> On Sep 06, 2004 06:53 PM, Zack Weinberg <zack@codesourcery.com> wrote:
>>> It breaks parallel make for me.
>> 
>> Changes to commands can't break parallel make; the bug is elsewhere.
>> Please say how it failed.
> 
> It breaks when building bitmap.o, but insn-conditions.h and
> another insn-something-file were not yet generated.
> 
> Gr.
> Steven

Is this occuring during stage2?

If so it is, as far as I can guess, the same apparent gmake bug that prevented me 
from committing an essentially approved patch which IMO would have had a side 
effect of solving Mohan's gcc-none.o problem more elegantly than his patch does.

http://gcc.gnu.org/ml/gcc-patches/2004-08/msg02155.html

The problem with its generic rules, make sometimes fails to serialize something that 
seems to be clearly is written out in the make file.

Essentially one of the insn-*.h files is getting rebuilt at the same time as an .o 
file that needs it, but that file does in fact list that .h file on its dependencies.

I circumvented the problem with a followup to the patch which didn't 
unnecessarily erase the generated *.[ch] files.  Nathanael was hesitant 
on that idea though.

Worse my original concept of only building those helper programs only once 
goes against the philosophy of the toplevel bootstrap.  It seems that in 
order to implement it, those files intended only to be built by the build 
compiler would probably have to be move to the toplevel.  

File a PR, cc: it to me and I'll look at another way to kludge around it tonight.

Kelley Cook

  reply	other threads:[~2004-09-07 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-06 16:18 Steven Bosscher
2004-09-06 16:53 ` Zack Weinberg
2004-09-06 18:40   ` Steven Bosscher
2004-09-07 18:16     ` Kelley Cook [this message]
2004-09-07 18:52       ` Zack Weinberg
2004-09-07 18:54       ` Mohan Embar
2004-09-07 19:45       ` Mohan Embar

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=413DFB10.8070009@gcc.gnu.org \
    --to=kcook@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=membar@gcc.gnu.org \
    --cc=neroden@twcny.rr.com \
    --cc=stevenb@suse.de \
    --cc=zack@codesourcery.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).