public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [Ada] Fix parallel LTO bootstrap
Date: Mon, 04 Jul 2011 09:49:00 -0000	[thread overview]
Message-ID: <20110704094859.GD26368@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <201107012347.51145.ebotcazou@adacore.com>

> Not clear why this never showed up on the 4.6 branch, but this now prevents a 
> parallel LTO bootstrap with Ada enabled from completing on the mainline.
> 
> Parallel LTO-bootstrapped, applied on the mainline and 4.6 branch.
> 
> 
> 2011-07-01  Eric Botcazou  <ebotcazou@adacore.com>
> 
> 	* gcc-interface/Make-lang.in (gnat1): Prepend '+' to the command.
> 	(gnatbind): Likewise.

The changle is obviously correct, but I wonder how the bootstrap dies w/o '+'.
It should IMO just prevent the parallelizm and take longer.

Honza

  reply	other threads:[~2011-07-04  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 21:47 Eric Botcazou
2011-07-04  9:49 ` Jan Hubicka [this message]
2011-07-04 10:22   ` Eric Botcazou

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=20110704094859.GD26368@atrey.karlin.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.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).