public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/43170] gcc 4.5 20100218 bootstrap compare fails on os x 10.6
Date: Sun, 28 Feb 2010 12:32:00 -0000	[thread overview]
Message-ID: <20100228123230.5273.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43170-14181@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from dominiq at lps dot ens dot fr  2010-02-28 12:32 -------
(In reply to comment #8)
> Thank you, very well.  Can you (or somebody else who sees the failure with -jN,
> N>1) try a bootstrap on x86_64-apple-darwin10 with non-parallel make from a
> clean directory?

I don't understand what you are expecting. Since the parallel bootstrap works
most of the time, why are you expecting the non-parallel one to always fail? It
seems to me highly unlikely. Note that a bootstrap with only gcc and gfortran
takes about 1 hour in parallel, so probably ~2 hours in non-parallel.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43170


  parent reply	other threads:[~2010-02-28 12:32 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 21:53 [Bug bootstrap/43170] New: " hal at oz dot net
2010-02-24 21:55 ` [Bug bootstrap/43170] " pinskia at gcc dot gnu dot org
2010-02-24 22:06 ` hal at oz dot net
2010-02-24 23:07 ` dominiq at lps dot ens dot fr
2010-02-28 11:00 ` dominiq at lps dot ens dot fr
2010-02-28 11:15 ` rwild at gcc dot gnu dot org
2010-02-28 11:30 ` dominiq at lps dot ens dot fr
2010-02-28 11:42 ` rwild at gcc dot gnu dot org
2010-02-28 11:59 ` dominiq at lps dot ens dot fr
2010-02-28 12:22 ` rwild at gcc dot gnu dot org
2010-02-28 12:32 ` dominiq at lps dot ens dot fr [this message]
2010-02-28 15:39 ` dominiq at lps dot ens dot fr
2010-02-28 18:14 ` rwild at gcc dot gnu dot org
2010-03-12 10:38 ` dominiq at lps dot ens dot fr
2010-03-13  9:12 ` rwild at gcc dot gnu dot org
2010-03-13  9:14 ` rwild at gcc dot gnu dot org
2010-03-13 10:56 ` dominiq at lps dot ens dot fr
2010-04-15 22:16 ` dominiq at lps dot ens dot fr
2010-04-15 22:19 ` steven at gcc dot gnu dot org
2010-04-16  0:44 ` danp57 at optonline dot net
2010-04-16  1:06 ` danp57 at optonline dot net
2010-04-16  5:17 ` rwild at gcc dot gnu dot org
2010-04-16  9:49 ` danp57 at optonline dot net
2010-04-16 12:07 ` dominiq at lps dot ens dot fr
2010-04-16 13:27 ` danp57 at optonline dot net
2010-04-16 13:52 ` howarth at nitro dot med dot uc dot edu
2010-04-16 14:35 ` dominiq at lps dot ens dot fr
2010-04-16 15:27 ` danp57 at optonline dot net
2010-04-16 17:06 ` danp57 at optonline dot net
2010-05-28 12:17 ` dominiq at lps dot ens dot fr
2010-05-29  7:47 ` iains at gcc dot gnu dot org
2010-06-02  8:59 ` dominiq at lps dot ens dot fr
2010-06-02  9:25 ` iains at gcc dot gnu dot org
2010-06-02  9:35 ` dominiq at lps dot ens dot fr
2010-06-02  9:45 ` iains at gcc dot gnu dot org
2010-06-02  9:54 ` dominiq at lps dot ens dot fr
2010-06-02 10:06 ` iains at gcc dot gnu dot org
2010-06-02 10:17 ` dominiq at lps dot ens dot fr
2010-06-02 17:05 ` rwild at gcc dot gnu dot org
2010-06-02 17:09 ` dominiq at lps dot ens dot fr
2010-06-02 17:40 ` Ralf dot Wildenhues at gmx dot de
2010-06-02 18:22 ` dominiq at lps dot ens dot fr
2010-06-02 18:36 ` dominiq at lps dot ens dot fr
2010-06-02 19:06 ` dominiq at lps dot ens dot fr
2010-06-02 19:16 ` iains at gcc dot gnu dot org
2010-06-02 19:42 ` iains at gcc dot gnu dot org
2010-06-02 20:08 ` dominiq at lps dot ens dot fr
2010-06-02 20:09 ` iains at gcc dot gnu dot org
2010-06-02 20:13 ` iains at gcc dot gnu dot org
2010-06-02 20:19 ` dominiq at lps dot ens dot fr
2010-06-02 20:29 ` iains at gcc dot gnu dot org
2010-06-02 20:32 ` iains at gcc dot gnu dot org
2010-06-02 20:39 ` dominiq at lps dot ens dot fr
2010-06-02 20:44 ` iains at gcc dot gnu dot org
2010-06-02 20:59 ` dominiq at lps dot ens dot fr
2010-06-02 22:07 ` iains at gcc dot gnu dot org
2010-06-03  5:53 ` rwild at gcc dot gnu dot org
2010-06-03  7:58 ` iains at gcc dot gnu dot org
2010-06-03  9:11 ` jakub at gcc dot gnu dot org
2010-06-03 10:34 ` rwild at gcc dot gnu dot org
2010-06-03 10:47 ` jakub at gcc dot gnu dot org
2010-06-03 10:59 ` iains at gcc dot gnu dot org
2010-06-03 12:50 ` iains at gcc dot gnu dot org
2010-06-03 13:04 ` howarth at nitro dot med dot uc dot edu
2010-06-03 13:18 ` iains at gcc dot gnu dot org
2010-06-03 13:46 ` howarth at nitro dot med dot uc dot edu
2010-06-03 16:13 ` iains at gcc dot gnu dot org
2010-06-03 16:58 ` jakub at gcc dot gnu dot org
2010-06-03 18:20 ` howarth at nitro dot med dot uc dot edu
2010-06-03 18:23 ` dominiq at lps dot ens dot fr
2010-06-03 19:02 ` jakub at gcc dot gnu dot org
2010-06-03 20:07 ` iains at gcc dot gnu dot org
2010-06-04  0:40 ` iains at gcc dot gnu dot org
2010-06-06 13:35 ` iains at gcc dot gnu dot org
2010-06-09  9:27 ` iains at gcc dot gnu dot org
2010-06-10  9:02 ` iains at gcc dot gnu dot org
2010-06-11  8:38 ` iains at gcc dot gnu dot org
     [not found] <bug-43170-4@http.gcc.gnu.org/bugzilla/>
2010-10-21  5:43 ` pinskia at gcc dot gnu.org
2010-10-28 20:10 ` pinskia at gcc dot gnu.org

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=20100228123230.5273.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).