From: Tim Prince <n8tm@aol.com>
To: gcc@gcc.gnu.org
Subject: Re: End of GCC 4.6 Stage 1: October 27, 2010
Date: Mon, 06 Sep 2010 16:33:00 -0000 [thread overview]
Message-ID: <4C8517B1.1020909@aol.com> (raw)
In-Reply-To: <AANLkTinCNxzQKMrsFNK3vQSGRrO7se5Sh_iO9uw=dTGS@mail.gmail.com>
On 9/6/2010 9:21 AM, Richard Guenther wrote:
> On Mon, Sep 6, 2010 at 6:19 PM, NightStrike<nightstrike@gmail.com> wrote:
>> On Mon, Sep 6, 2010 at 5:21 AM, Richard Guenther<rguenther@suse.de> wrote:
>>> On Mon, 6 Sep 2010, Tobias Burnus wrote:
>>>
>>>> Gerald Pfeifer wrote:
>>>>> Do you have a pointer to testresults you'd like us to use for reference?
>>>>>
>>>>> From our release criteria, for secondary platforms we have:
>>>>>
>>>>> • The compiler bootstraps successfully, and the C++ runtime library
>>>>> builds.
>>>>> • The DejaGNU testsuite has been run, and a substantial majority of the
>>>>> tests pass.
>>>> See for instance:
>>>> http://gcc.gnu.org/ml/gcc-testresults/2010-09/msg00295.html
>>> There are no libstdc++ results in that.
>>>
>>> Richard.
>> This is true. I always run make check-gcc. What should I be doing instead?
> make -k check
make check-c++ runs both g++ and libstdc++-v3 testsuites.
--
Tim Prince
next prev parent reply other threads:[~2010-09-06 16:33 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 [this message]
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
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=4C8517B1.1020909@aol.com \
--to=n8tm@aol.com \
--cc=gcc@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).