From: Dennis Clarke <dclarke@blastwave.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Ian Lance Taylor <iant@google.com>, gcc-help@gcc.gnu.org
Subject: Re: GCC 4.7.2 stage3 bootstrap error on RHEL6 : collect2: error: ld returned 1 exit status
Date: Wed, 19 Dec 2012 19:21:00 -0000 [thread overview]
Message-ID: <fb8c54362911.50d1cd5c@blastwave.org> (raw)
In-Reply-To: <CAH6eHdRTss4Kb-Tt27nNBYSarVQiN9QZ6Y6U+NGqP39u=5kkuw@mail.gmail.com>
> >> Depends on how much trust you place in -jX for X>1 and in my case,
> not much, yet.
> >
> > Why?
>
> The reason for my question is that you keep mentioning the time it
> takes to do a bootstrap or testsuite, which seems a bit pointless when
> there's a proven way to speed it up that you're not using. If you
> care about the time use -j, but if you don't, why keep mentioning it?
The time is not an interest, only a yardstick to tell me when to look for a result. The quality of the result is what is of great interest to me and GCC 4.7.2 is really not a good quality result, at least not that I have seen other than on a really really old Solaris 8 i386 box.
The time is of interest only because now I know that I can look for a result in six or seven hours and know on the wall clock when to care about looking. This is running on a machine that I use for other things so running a build with -j 8 would sort of kill the box for a while.
Dennis
prev parent reply other threads:[~2012-12-19 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 22:17 GCC 2.7.2 " Dennis Clarke
2012-12-18 7:10 ` Ian Lance Taylor
2012-12-18 17:39 ` Dennis Clarke
2012-12-19 4:32 ` Dennis Clarke
2012-12-19 13:47 ` Jonathan Wakely
2012-12-19 16:58 ` GCC 4.7.2 " Dennis Clarke
2012-12-19 17:19 ` Jonathan Wakely
2012-12-19 17:28 ` Jonathan Wakely
2012-12-19 19:21 ` Dennis Clarke [this message]
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=fb8c54362911.50d1cd5c@blastwave.org \
--to=dclarke@blastwave.org \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
--cc=jwakely.gcc@gmail.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).