From: Olivier Hainque <hainque@adacore.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: fix libcc1 dependencies in toplevel Makefile
Date: Thu, 15 Jun 2017 12:29:00 -0000 [thread overview]
Message-ID: <E4B30A80-41CF-44ED-AF27-3A915869E2F3@adacore.com> (raw)
In-Reply-To: <9937e0ec-f802-5d26-83cf-922daa3a4024@acm.org>
> On 15 Jun 2017, at 14:03, Nathan Sidwell <nathan@acm.org> wrote:
>
> On 06/14/2017 01:24 PM, Olivier Hainque wrote:
>
>>> I'm happy to try the patch.
>> That would bring useful extra datapoints, Thanks!
>
> I now seem unable to trigger the race with an unpatched source. Sorry
No pb. Thanks for trying.
We were seeing the failures only in pretty specific circumstances (particular
machine & load conditions etc)
The patch remains worth considering IMO. At least, it would be interesting to
get feedback from a build-system maintainer on the correctness of the current
dependencies.
Our understanding is that it is incorrect to have libcc1 depend on
maybe-all-gcc in a bootstrapping setup because it can trigger rebuilds of gcc/
components in parallel with ongoing processing of target components (with
pre-requisites on stage_current only).
next prev parent reply other threads:[~2017-06-15 12:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 12:58 Olivier Hainque
2017-06-14 11:39 ` Nathan Sidwell
2017-06-14 21:11 ` Olivier Hainque
2017-06-15 12:03 ` Nathan Sidwell
2017-06-15 12:29 ` Olivier Hainque [this message]
2017-06-22 12:13 ` Alexandre Oliva
2017-06-26 7:41 ` Olivier Hainque
2017-06-27 16:32 ` Olivier Hainque
2017-06-27 19:53 ` Alexandre Oliva
2017-07-03 21:05 ` Olivier Hainque
2018-06-03 19:13 ` Alexandre Oliva
2018-06-12 2:50 ` Alexandre Oliva
2018-06-12 8:57 ` Olivier Hainque
2018-06-12 15:31 ` Jeff Law
2018-06-26 5:39 ` Alexandre Oliva
2018-06-27 19:53 ` Olivier Hainque
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=E4B30A80-41CF-44ED-AF27-3A915869E2F3@adacore.com \
--to=hainque@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.org \
/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).