public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/36292] New: [4.4 Regression]: Many failures in gcc.dg/pch/
Date: Wed, 21 May 2008 16:30:00 -0000 [thread overview]
Message-ID: <bug-36292-682@http.gcc.gnu.org/bugzilla/> (raw)
Revision 135708 has many failures in gcc.dg/pch/ on Linux/ia32:
FAIL: gcc.dg/pch/counter-2.c -O0 -g
FAIL: gcc.dg/pch/counter-2.c -O0
FAIL: gcc.dg/pch/counter-2.c -O1
FAIL: gcc.dg/pch/counter-2.c -O2
FAIL: gcc.dg/pch/counter-2.c -O3 -fomit-frame-pointer
FAIL: gcc.dg/pch/counter-2.c -O3 -g
FAIL: gcc.dg/pch/counter-2.c -Os
FAIL: gcc.dg/pch/valid-1.c -O0 -g
FAIL: gcc.dg/pch/valid-1.c -O0
FAIL: gcc.dg/pch/valid-1.c -O1
FAIL: gcc.dg/pch/valid-1.c -O2
FAIL: gcc.dg/pch/valid-1.c -O3 -fomit-frame-pointer
FAIL: gcc.dg/pch/valid-1.c -O3 -g
FAIL: gcc.dg/pch/valid-1.c -Os
FAIL: gcc.dg/pch/valid-2.c -O0 -g
FAIL: gcc.dg/pch/valid-2.c -O0
FAIL: gcc.dg/pch/valid-2.c -O1
FAIL: gcc.dg/pch/valid-2.c -O2
FAIL: gcc.dg/pch/valid-2.c -O3 -fomit-frame-pointer
FAIL: gcc.dg/pch/valid-2.c -O3 -g
FAIL: gcc.dg/pch/valid-2.c -Os
FAIL: gcc.dg/pch/valid-3.c -O0 -g
FAIL: gcc.dg/pch/valid-3.c -O0
FAIL: gcc.dg/pch/valid-3.c -O1
FAIL: gcc.dg/pch/valid-3.c -O2
FAIL: gcc.dg/pch/valid-3.c -O3 -fomit-frame-pointer
FAIL: gcc.dg/pch/valid-3.c -O3 -g
FAIL: gcc.dg/pch/valid-3.c -Os
FAIL: gcc.dg/pch/warn-1.c -O0 -g
FAIL: gcc.dg/pch/warn-1.c -O0
FAIL: gcc.dg/pch/warn-1.c -O1
FAIL: gcc.dg/pch/warn-1.c -O2
FAIL: gcc.dg/pch/warn-1.c -O3 -fomit-frame-pointer
FAIL: gcc.dg/pch/warn-1.c -O3 -g
FAIL: gcc.dg/pch/warn-1.c -Os
Revision 135705 is OK. Revision 135708:
http://gcc.gnu.org/ml/gcc-cvs/2008-05/msg00870.html
may be the cause.
--
Summary: [4.4 Regression]: Many failures in gcc.dg/pch/
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: hjl dot tools at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36292
next reply other threads:[~2008-05-21 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 16:30 hjl dot tools at gmail dot com [this message]
2008-05-21 16:35 ` [Bug testsuite/36292] " hjl dot tools at gmail dot com
2008-05-21 17:02 ` nathan at gcc dot gnu dot org
2008-05-21 21:46 ` pinskia at gcc dot gnu dot org
2008-05-22 6:34 ` nathan at gcc dot gnu dot 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=bug-36292-682@http.gcc.gnu.org/bugzilla/ \
--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).