From: Andreas Jaeger <aj@suse.de>
To: Nathanael Nerode <neroden@gcc.gnu.org>
Cc: gcc@gcc.gnu.org
Subject: What happened to the GCC 3.3 testsuite?
Date: Thu, 11 Dec 2003 20:21:00 -0000 [thread overview]
Message-ID: <u8y8tjt9md.fsf@gromit.moeb> (raw)
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
Just compare these two summaries:
=== gcc Summary ===
# of expected passes 21248
# of unexpected failures 1
# of expected failures 69
# of unsupported tests 91
/builds/gcc/misc/gcc/xgcc version 3.3.3 20031208 (prerelease)
=== gcc Summary ===
# of expected passes 15165
# of expected failures 22
# of unsupported tests 1
/builds/gcc/misc/gcc/xgcc version 3.3.3 20031211 (prerelease)
Apparently 6000 tests have disappeared between these two days!
I see in the newer gcc.sum file at the end:
ERROR: (DejaGnu) proc "scan-file xwin1.i {(^|
)#if 0}" does not exist.
This seems to be related to:
2003-12-10 Nathanael Nerode <neroden@gcc.gnu.org>
Backport from mainline:
* gcc.dg/cpp/trad/xwin1.c: New test case.
So, what's happening here? Do we need to backport also the following
patch (from mainline):
2003-06-02 Mark Mitchell <mark@codesourcery.com>
* lib/scanasm.exp (dg-scan): New function, factored out of ...
(scan-assembler): ... here. Use dg-scan.
(scan-assembler-not): Likewise.
(scan-file): New function.
(scan-file-not): Likewise.
Nathanael, can you look at these, please?
Cheers,
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2003-12-11 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 20:21 Andreas Jaeger [this message]
2003-12-12 0:38 ` Gabriel Dos Reis
2003-12-12 13:33 ` Nathanael Nerode
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=u8y8tjt9md.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=neroden@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).