Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: "J.T. Conklin" <jtc@redback.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA]: simulator build failures with parallel make
Date: Sun, 15 Apr 2001 13:56:00 -0000	[thread overview]
Message-ID: <20010415135646.A25615@lucon.org> (raw)
In-Reply-To: <5mn19hc2lc.fsf@jtc.redback.com>

On Sun, Apr 15, 2001 at 01:47:27PM -0700, J.T. Conklin wrote:
> >>>>> "HJ" == H J Lu <hjl@lucon.org> writes:
> >>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
> Andrew> With that dependency added without -j does the generator get
> Andrew> run twice?  I've this memory of a strange querk with make
> Andrew> dependencies and files being created as a sideeffect.
> >> 
> >> No.  
> >> 
> >> But now that you've mentioned it, I recall that rules with multiple
> >> targets will be executed once per target with -j (at least with GNU
> >> make).  This can be worked around by creating a psuedo-target to 
> 
> HJ> Please don't add any workaround.  Just provide complete
> HJ> dependencies, [...]
> 
> And just what workaround do you think I'm adding? 
> 
> HJ> [...] any make, including GNU make, will be happy.
> 
> Untrue.  GNU make will invoke the commands for a rule with multiple
> targets multiple times when used with -j.  Bug or feature, this must
> be accomidated.
> 
> For example:
> 
>         $ cat Makefile
>         all: foo.tab.c foo.tab.h
> 
>         foo.tab.c foo.tab.h: foo.y
>                 $(YACC) -b foo -p foo -d $?
> 
>         $ gmake -j
>         yacc -b foo -p foo -d foo.y
>         yacc -b foo -p foo -d foo.y
> 
> In many cases, this must be guarded against.  A rule with two targets
> occured only once in the four simulator makefiles I touched. And that
> one already handled it by introducing a pseudo-target to serialize 
> the make.  For the above makefile, the equivalent would be:
> 
>         $ cat Makefile
>         all: foo.tab.c foo.tab.h
> 
>         foo.tab.c foo.tab.h: foo-stamp
> 
>         foo-stamp: foo.y
>                 $(YACC) -b foo -p foo -d $?
>                 touch $@
> 
> So what exactly is your complaint about my patch.
> 

That is a bug in Makefile and that is why we have ylwrap. See how it is
done in ld/Makefile.*, binutils/Makefile.* and gas/Makefile.*. Do

# grep YLWRAP */Makefile.in

in binutils tree. I can anaswer any questions if those Makefile.in
files are not clear enough.


H.J.


  reply	other threads:[~2001-04-15 13:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 12:26 J.T. Conklin
2001-04-06 11:08 ` Andrew Cagney
2001-04-06 11:30   ` Frank Ch. Eigler
2001-04-08 23:28     ` Eli Zaretskii
2001-04-15 12:54   ` J.T. Conklin
2001-04-15 13:13     ` H . J . Lu
2001-04-15 13:47       ` J.T. Conklin
2001-04-15 13:56         ` H . J . Lu [this message]
2001-04-15 22:53           ` Eli Zaretskii

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=20010415135646.A25615@lucon.org \
    --to=hjl@lucon.org \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=jtc@redback.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