From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: Andrew Haley <aph@redhat.com>,
Richard Guenther <richard.guenther@gmail.com>,
Richard Guenther <rguenther@suse.de>,
Tobias Burnus <burnus@net-b.de>,
Gerald Pfeifer <gerald@pfeifer.com>,
Mark Mitchell <mark@codesourcery.com>, GCC <gcc@gcc.gnu.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: End of GCC 4.6 Stage 1: October 27, 2010
Date: Tue, 21 Sep 2010 10:01:00 -0000 [thread overview]
Message-ID: <AANLkTinJkxUTL4AOLUrGNHZvG5GSuUn=6VDQegwSb+8Y@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikBvrdvLLFhybbiXgcpaOE2fk1wgGDSQT7g7sRm@mail.gmail.com>
On 20 September 2010 17:33, NightStrike wrote:
>
> Ok, so it took a while to eventually find out that cygwin still
> malfunctions with -j, and I get lots of "fork() blows because it can't
> figure out how to find ubiquitous resources" errors. However, I
> eventually got this to finish:
>
> http://gcc.gnu.org/ml/gcc-testresults/2010-09/msg01864.html
>
> So there's a complete testsuite that includes libstdc++ this time. I
> will now have this running continuously.
>
> Note that you won't see results every day -- it takes a LONG time to
> do this, mostly because I can't do -j on cygwin. I imagine results
> will be every 4 days or so if I run continuously.
>
> Is this enough now for us to qualify?
Could you send me your libstdc++.log file?
I'm curious about some of the libstdc++ failures, which are in pretty
simple tests that shouldn't be target dependent. There might be
something simple in testsuite_hooks.h or another common file that
causes all those failures.
next prev parent reply other threads:[~2010-09-20 18:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 22:55 Mark Mitchell
2010-09-05 4:23 ` NightStrike
2010-09-05 18:03 ` Mark Mitchell
2010-09-05 18:23 ` NightStrike
2010-09-05 18:29 ` Mark Mitchell
2010-09-05 18:35 ` NightStrike
2010-09-05 18:40 ` Mark Mitchell
2010-09-05 22:10 ` Gerald Pfeifer
2010-09-05 22:18 ` Tobias Burnus
2010-09-06 9:22 ` Richard Guenther
2010-09-06 16:19 ` NightStrike
2010-09-06 16:21 ` Richard Guenther
2010-09-06 16:33 ` Tim Prince
2010-09-06 17:18 ` NightStrike
2010-09-06 17:24 ` Andrew Haley
2010-09-06 17:32 ` NightStrike
2010-09-20 23:23 ` NightStrike
2010-09-21 10:01 ` Jonathan Wakely [this message]
2010-09-21 15:09 ` NightStrike
2010-09-21 17:27 ` Dave Korn
2010-09-23 22:09 ` NightStrike
2010-10-08 15:56 ` NightStrike
2010-10-08 16:06 ` Jonathan Wakely
2010-10-08 16:10 ` Kai Tietz
2010-10-08 16:54 ` NightStrike
2010-10-08 18:04 ` Jonathan Wakely
2010-10-08 18:11 ` NightStrike
2010-10-09 1:40 ` Dave Korn
2011-02-24 17:05 ` NightStrike
2010-10-08 21:09 ` Richard Guenther
2010-10-08 21:14 ` NightStrike
2010-10-09 0:42 ` Richard Guenther
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='AANLkTinJkxUTL4AOLUrGNHZvG5GSuUn=6VDQegwSb+8Y@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=aph@redhat.com \
--cc=burnus@net-b.de \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=mark@codesourcery.com \
--cc=nightstrike@gmail.com \
--cc=rguenther@suse.de \
--cc=richard.guenther@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).