public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug inline-asm/19226] New: ICE in g++.old-deja/g++.pt/asm1.C and asm2.C with -fpic/-fPIC Date: Sun, 02 Jan 2005 16:58:00 -0000 [thread overview] Message-ID: <20050102165832.19226.ghazi@gcc.gnu.org> (raw) When running the GCC testsuite on i686-pc-linux-gnu using -fpic or -fPIC, I get additional failures with 3.3, 3.4 and mainline: FAIL: g++.old-deja/g++.pt/asm1.C (test for excess errors) FAIL: g++.old-deja/g++.pt/asm2.C (test for excess errors) as shown here: http://gcc.gnu.org/ml/gcc-testresults/2005-01/msg00029.html http://gcc.gnu.org/ml/gcc-testresults/2005-01/msg00085.html http://gcc.gnu.org/ml/gcc-testresults/2005-01/msg00084.html Both of these tests fail like this: g++.old-deja/g++.pt/asm1.C:6: error: can't find a register in class `BREG' while reloading `asm' Is there something to fix in the compiler, the testcase, or should the test be bypassed when using -fpic/-fPIC ? -- Summary: ICE in g++.old-deja/g++.pt/asm1.C and asm2.C with - fpic/-fPIC Product: gcc Version: 3.3.6 Status: UNCONFIRMED Severity: normal Priority: P2 Component: inline-asm AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ghazi at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19226
next reply other threads:[~2005-01-02 16:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-02 16:58 ghazi at gcc dot gnu dot org [this message] 2005-01-02 17:04 ` [Bug target/19226] " pinskia at gcc dot gnu dot org 2005-01-02 17:18 ` kghazi at verizon dot net 2005-01-03 15:11 ` pinskia at gcc dot gnu dot org 2005-01-05 16:38 ` ghazi at gcc dot gnu dot org 2005-01-06 2:37 ` ghazi at gcc dot gnu dot org 2005-01-06 5:52 ` [Bug target/19226] [3.4 only] " pinskia at gcc dot gnu dot org 2005-05-19 17:42 ` mmitchel 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=20050102165832.19226.ghazi@gcc.gnu.org \ --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).