public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/19232] New: Failure in gcc.dg/assign-warn-3.c on i686-pc-linux-gnu with -fpic/-fPIC
@ 2005-01-02 18:25 ghazi at gcc dot gnu dot org
2005-01-03 15:31 ` [Bug target/19232] " pinskia at gcc dot gnu dot org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: ghazi at gcc dot gnu dot org @ 2005-01-02 18:25 UTC (permalink / raw)
To: gcc-bugs
When running the testsuite with mainline on i686-pc-linux-gnu with -fpic or -
fPIC, I get the following additional failures:
FAIL: gcc.dg/assign-warn-3.c (test for warnings, line 9)
FAIL: gcc.dg/assign-warn-3.c (test for warnings, line 13)
The expected warnings simply fail to appear with the extra flag. Warning
output should not be affected by this.
--
Summary: Failure in gcc.dg/assign-warn-3.c on i686-pc-linux-gnu
with -fpic/-fPIC
Product: gcc
Version: 4.0.0
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=19232
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug target/19232] Failure in gcc.dg/assign-warn-3.c on i686-pc-linux-gnu with -fpic/-fPIC
2005-01-02 18:25 [Bug target/19232] New: Failure in gcc.dg/assign-warn-3.c on i686-pc-linux-gnu with -fpic/-fPIC ghazi at gcc dot gnu dot org
@ 2005-01-03 15:31 ` pinskia at gcc dot gnu dot org
2005-01-03 17:37 ` reichelt at gcc dot gnu dot org
2005-01-03 17:59 ` pinskia at gcc dot gnu dot org
2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-01-03 15:31 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-03 15:31 -------
I cannot reproduce this with a cross from a couple of days ago.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19232
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug target/19232] Failure in gcc.dg/assign-warn-3.c on i686-pc-linux-gnu with -fpic/-fPIC
2005-01-02 18:25 [Bug target/19232] New: Failure in gcc.dg/assign-warn-3.c on i686-pc-linux-gnu with -fpic/-fPIC ghazi at gcc dot gnu dot org
2005-01-03 15:31 ` [Bug target/19232] " pinskia at gcc dot gnu dot org
@ 2005-01-03 17:37 ` reichelt at gcc dot gnu dot org
2005-01-03 17:59 ` pinskia at gcc dot gnu dot org
2 siblings, 0 replies; 4+ messages in thread
From: reichelt at gcc dot gnu dot org @ 2005-01-03 17:37 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From reichelt at gcc dot gnu dot org 2005-01-03 17:36 -------
With today's mainline I get the following results which confirm
Kaveh's observations:
gcc -c -O assign-warn-3.c: no warning
gcc -c -O2 assign-warn-3.c: no warning
gcc -c -O3 assign-warn-3.c: warning
gcc -c -O assign-warn-3.c -fpic: no warning
gcc -c -O2 assign-warn-3.c -fpic: no warning
gcc -c -O3 assign-warn-3.c -fpic: no warning !!!
That no warning is emitted with -O and -O2 is expected since no
inlining takes place.
Just for curiosity I marked f0 and f1 in the test as inline and
got the following results:
gcc -c -O assign-warn-3.c: no warning !!!
gcc -c -O2 assign-warn-3.c: warning
gcc -c -O3 assign-warn-3.c: warning
gcc -c -O assign-warn-3.c -fpic: warning
gcc -c -O2 assign-warn-3.c -fpic: warning
gcc -c -O3 assign-warn-3.c -fpic: warning
Here I'd expect a warning in all six cases.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |reichelt at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Keywords| |diagnostic
Last reconfirmed|0000-00-00 00:00:00 |2005-01-03 17:36:58
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19232
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug target/19232] Failure in gcc.dg/assign-warn-3.c on i686-pc-linux-gnu with -fpic/-fPIC
2005-01-02 18:25 [Bug target/19232] New: Failure in gcc.dg/assign-warn-3.c on i686-pc-linux-gnu with -fpic/-fPIC ghazi at gcc dot gnu dot org
2005-01-03 15:31 ` [Bug target/19232] " pinskia at gcc dot gnu dot org
2005-01-03 17:37 ` reichelt at gcc dot gnu dot org
@ 2005-01-03 17:59 ` pinskia at gcc dot gnu dot org
2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-01-03 17:59 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-03 17:59 -------
(In reply to comment #2)
> With today's mainline I get the following results which confirm
> Kaveh's observations:
>
> gcc -c -O assign-warn-3.c: no warning
> gcc -c -O2 assign-warn-3.c: no warning
> gcc -c -O3 assign-warn-3.c: warning
> gcc -c -O assign-warn-3.c -fpic: no warning
> gcc -c -O2 assign-warn-3.c -fpic: no warning
> gcc -c -O3 assign-warn-3.c -fpic: no warning !!!
To repsond to this one, with -fpic/PIC we don't inline functions which can be overridden by other TUs.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19232
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-01-03 17:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-01-02 18:25 [Bug target/19232] New: Failure in gcc.dg/assign-warn-3.c on i686-pc-linux-gnu with -fpic/-fPIC ghazi at gcc dot gnu dot org
2005-01-03 15:31 ` [Bug target/19232] " pinskia at gcc dot gnu dot org
2005-01-03 17:37 ` reichelt at gcc dot gnu dot org
2005-01-03 17:59 ` pinskia 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).