public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/19229] New: Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu
@ 2005-01-02 17:34 ghazi at gcc dot gnu dot org
2005-01-02 17:59 ` [Bug target/19229] " ghazi at gcc dot gnu dot org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: ghazi at gcc dot gnu dot org @ 2005-01-02 17:34 UTC (permalink / raw)
To: gcc-bugs
When running the testsuite on 3.3 with -fpic or -fPIC I get the following
additional error:
FAIL: gcc.dg/asm-names.c (test for excess errors)
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
The error message from the logfile is:
/tmp/ccofal7Q.o: In function `_main':
/tmp/ccofal7Q.o(.text+0x13): undefined reference to `__GLOBAL_OFFSET_TABLE_'
/tmp/ccofal7Q.o: In function `main':
/tmp/ccofal7Q.o(.text+0x4a): undefined reference to `__GLOBAL_OFFSET_TABLE_'
/tmp/ccofal7Q.o: In function `___main':
/tmp/ccofal7Q.o(.text+0x67): undefined reference to `__GLOBAL_OFFSET_TABLE_'
collect2: ld returned 1 exit status
Note the testcase has changed in 3.4 and 4.0 to mask the error, but the
original testcase fails the same way with those newer compilers. I could
update the testcase on the 3.3 branch to what it is on mainline if that makes
sense.
Is there something to fix in the compiler, the testcase, or should the test be
bypassed when using -fpic/-fPIC ?
--
Summary: Error in gcc.dg/asm-names.c when using -fpic/-fPIC on
i686-pc-linux-gnu
Product: gcc
Version: 3.3.6
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: target
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=19229
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/19229] Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu
2005-01-02 17:34 [Bug target/19229] New: Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu ghazi at gcc dot gnu dot org
@ 2005-01-02 17:59 ` ghazi at gcc dot gnu dot org
2005-01-03 15:19 ` pinskia at gcc dot gnu dot org
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: ghazi at gcc dot gnu dot org @ 2005-01-02 17:59 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From ghazi at gcc dot gnu dot org 2005-01-02 17:58 -------
*** Bug 19230 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19229
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/19229] Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu
2005-01-02 17:34 [Bug target/19229] New: Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu ghazi at gcc dot gnu dot org
2005-01-02 17:59 ` [Bug target/19229] " ghazi at gcc dot gnu dot org
@ 2005-01-03 15:19 ` pinskia at gcc dot gnu dot org
2005-01-03 23:56 ` rth at gcc dot gnu dot org
2005-01-04 0:39 ` ghazi at gcc dot gnu dot org
3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-01-03 15:19 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-03 15:19 -------
Hmm, this looks more like a binutils bug rather than anything else.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19229
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/19229] Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu
2005-01-02 17:34 [Bug target/19229] New: Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu ghazi at gcc dot gnu dot org
2005-01-02 17:59 ` [Bug target/19229] " ghazi at gcc dot gnu dot org
2005-01-03 15:19 ` pinskia at gcc dot gnu dot org
@ 2005-01-03 23:56 ` rth at gcc dot gnu dot org
2005-01-04 0:39 ` ghazi at gcc dot gnu dot org
3 siblings, 0 replies; 5+ messages in thread
From: rth at gcc dot gnu dot org @ 2005-01-03 23:56 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From rth at gcc dot gnu dot org 2005-01-03 23:56 -------
Not really. Gcc and binutils must agree on what leading underscore convention
to use. On normal ELF systems, we're forcing them to disagree for this test case
so it's not really surprising that we run into problems.
I think the revised test case in 3.4/4.0 is definitely More Correct.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19229
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/19229] Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu
2005-01-02 17:34 [Bug target/19229] New: Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu ghazi at gcc dot gnu dot org
` (2 preceding siblings ...)
2005-01-03 23:56 ` rth at gcc dot gnu dot org
@ 2005-01-04 0:39 ` ghazi at gcc dot gnu dot org
3 siblings, 0 replies; 5+ messages in thread
From: ghazi at gcc dot gnu dot org @ 2005-01-04 0:39 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From ghazi at gcc dot gnu dot org 2005-01-04 00:39 -------
Okay thanks, I've backported the testcase to 3.3.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19229
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2005-01-04 0:39 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-01-02 17:34 [Bug target/19229] New: Error in gcc.dg/asm-names.c when using -fpic/-fPIC on i686-pc-linux-gnu ghazi at gcc dot gnu dot org
2005-01-02 17:59 ` [Bug target/19229] " ghazi at gcc dot gnu dot org
2005-01-03 15:19 ` pinskia at gcc dot gnu dot org
2005-01-03 23:56 ` rth at gcc dot gnu dot org
2005-01-04 0:39 ` ghazi at gcc dot gnu dot org
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).