public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/47822] New: [4.6 Regression] Multiple test suite failures due to revision 170321
Date: Sun, 20 Feb 2011 11:13:00 -0000 [thread overview]
Message-ID: <bug-47822-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47822
Summary: [4.6 Regression] Multiple test suite failures due to
revision 170321
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dominiq@lps.ens.fr
CC: hjl@gcc.gnu.org, rguenther@suse.de
Revision 170321 caused a lot of failures on the test suite on
x86_64-apple-darwin10 and moxie-unknown-elf (see
http://gcc.gnu.org/ml/gcc-testresults/2011-02/msg02205.html). They are all of
the form:
[macbook] f90/bug% gcc46
/opt/gcc/work/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1.c
/opt/gcc/work/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1-lib.c
/opt/gcc/work/gcc/testsuite/gcc.c-torture/execute/builtins/lib/main.c -flto
lto1: fatal error: target specific builtin not available
compilation terminated.
lto-wrapper: gcc46 returned 1 exit status
collect2: lto-wrapper returned 1 exit status
Reverting the revision fixes the failures.
This is pr seems related to pr47820.
next reply other threads:[~2011-02-20 10:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 11:13 dominiq at lps dot ens.fr [this message]
2011-02-20 14:54 ` [Bug target/47822] " rguenth at gcc dot gnu.org
2011-02-20 15:14 ` rguenth at gcc dot gnu.org
2011-02-20 15:21 ` dominiq at lps dot ens.fr
2011-02-20 15:49 ` rguenth at gcc dot gnu.org
2011-02-20 16:24 ` dominiq at lps dot ens.fr
2011-02-20 17:23 ` rguenth at gcc dot gnu.org
2011-02-20 17:28 ` rguenth at gcc dot gnu.org
2011-02-20 18:49 ` mrs at gcc dot gnu.org
2011-02-20 19:03 ` mrs at gcc dot gnu.org
2011-02-20 19:35 ` dominiq at lps dot ens.fr
2011-02-20 19:40 ` mikestump at comcast dot net
2011-02-20 19:54 ` dominiq at lps dot ens.fr
2011-02-20 20:40 ` howarth at nitro dot med.uc.edu
2011-02-21 5:14 ` mrs at gcc dot gnu.org
2011-02-21 9:45 ` rguenth at gcc dot gnu.org
2011-02-21 10:09 ` dominiq at lps dot ens.fr
2011-02-21 10:37 ` iains at gcc dot gnu.org
2011-02-21 11:19 ` rguenth at gcc dot gnu.org
2011-02-21 21:34 ` mikestump at comcast dot net
2011-02-21 21:38 ` mikestump at comcast dot net
2011-02-21 21:48 ` mrs at gcc dot gnu.org
2011-02-22 10:52 ` dominiq at lps dot ens.fr
2011-02-22 12:01 ` mikestump at comcast dot net
2011-02-22 12:37 ` mikestump at comcast dot net
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-47822-4@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).