public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gseanmcg at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/47038] New: gcc.dg/pr46685.c FAILs on Solaris 10/SPARC Date: Wed, 22 Dec 2010 04:12:00 -0000 [thread overview] Message-ID: <bug-47038-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47038 Summary: gcc.dg/pr46685.c FAILs on Solaris 10/SPARC Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: gseanmcg@gmail.com Executing on host: /var/opt/BUILD/gcc-trunk.2010-12-20/gcc/xgcc -B/var/opt/BUILD/gcc-trunk.2010-12-20/gcc/ /var/opt/SOURCES/gcc-trunk/gcc/testsuite/gcc.dg/pr46685.c -O2 -freorder-blocks-and-partition -fpic -S -o pr46685.s (timeout = 300) /var/opt/SOURCES/gcc-trunk/gcc/testsuite/gcc.dg/pr46685.c: In function '__sparc_get_pc_thunk.l7':^M <built-in>:0:0: error: __sparc_get_pc_thunk.l7 causes a section type conflict^M compiler exited with status 1 output is: /var/opt/SOURCES/gcc-trunk/gcc/testsuite/gcc.dg/pr46685.c: In function '__sparc_get_pc_thunk.l7':^M <built-in>:0:0: error: __sparc_get_pc_thunk.l7 causes a section type conflict^M FAIL: gcc.dg/pr46685.c (test for excess errors) Excess errors: <built-in>:0:0: error: __sparc_get_pc_thunk.l7 causes a section type conflict same error for -m32 and -m64
next reply other threads:[~2010-12-22 4:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-22 4:12 gseanmcg at gmail dot com [this message] 2010-12-22 16:27 ` [Bug target/47038] " gseanmcg at gmail dot com 2010-12-24 16:07 ` ebotcazou at gcc dot gnu.org 2010-12-24 16:09 ` ebotcazou at gcc dot gnu.org 2010-12-28 15:25 ` [Bug target/47038] [4.6 Regression] failure of gcc.dg/pr46685.c ebotcazou at gcc dot gnu.org 2010-12-30 21:31 ` ebotcazou at gcc dot gnu.org 2010-12-30 21:33 ` ebotcazou at gcc dot gnu.org 2011-01-03 12:07 ` ebotcazou at gcc dot gnu.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-47038-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: linkBe 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).