--- Comment #20 from rguenth at gcc dot gnu dot org 2008-05-03 15:29
---
Subject: Bug 34973
Author: rguenth
Date: Sat May 3 15:28:57 2008
New Revision: 134903
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=134903
Log:
2008-05-03 Richard Guenther <[EMAIL PROTECTED]>
--- Comment #19 from rguenth at gcc dot gnu dot org 2008-05-03 15:29
---
Fixed.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSIGNE
--- Comment #18 from rguenth at gcc dot gnu dot org 2008-05-03 15:26
---
Subject: Bug 34973
Author: rguenth
Date: Sat May 3 15:26:10 2008
New Revision: 134902
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=134902
Log:
2008-05-03 Richard Guenther <[EMAIL PROTECTED]>
--- Comment #17 from awalton at gnome dot org 2008-05-03 14:57 ---
(In reply to comment #15)
> Whoops. I can reproduce the
>
> fm-directory-view.c:8887: error: dereferencing type-punned pointer will break
> strict-aliasing rules
>
> errors with -O2.
>
Yes, of course, that's what we
--- Comment #16 from rguenth at gcc dot gnu dot org 2008-05-03 14:13
---
Err, simple. (-Wstrict-aliasing=0 works, but -Wno-strict-aliasing doesn't)
Index: opts.c
===
--- opts.c (revision 134849)
+++ opts.c (work
--- Comment #15 from rguenth at gcc dot gnu dot org 2008-05-03 14:06
---
Whoops. I can reproduce the
fm-directory-view.c:8887: error: dereferencing type-punned pointer will break
strict-aliasing rules
errors with -O2.
--
rguenth at gcc dot gnu dot org changed:
What
--- Comment #14 from rguenth at gcc dot gnu dot org 2008-05-03 14:05
---
This doesn't lookk like the strict-aliasing warning though, but
gcc-4.3 -S t.i -o /dev/null -Wall -Wmissing-declarations -Wmissing-prototypes
-Wnested-externs -Wpointer-arith -Wcast-align -Werror -Wno-pointer-sign
--- Comment #13 from awalton at gnome dot org 2008-05-03 13:59 ---
Created an attachment (id=15569)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15569&action=view)
preprocessor output (gzipped)
With "gcc (Ubuntu 4.3.0-3ubuntu4) 4.3.1 20080430 (prerelease)". This is what I
got fro
--- Comment #12 from rguenth at gcc dot gnu dot org 2008-05-03 12:18
---
We are still waiting for a testcase, which would be the preprocessed source of
the file triggering the warning. You'll get preprocessed source by appending
'-save-temps' to the gcc commandline and the preprocessed
--- Comment #11 from awalton at gnome dot org 2008-05-03 11:26 ---
I believe we're running into this in Nautilus and GCC 4.3.x (confirmed on both
Ubuntu Intrepid Ibex/8.10's 4.3 toolchain and Arch Linux's toolchain [unsure of
the micro-version]). If anyone wants to walk me through the st
--- Comment #10 from manu at gcc dot gnu dot org 2008-01-28 10:51 ---
(In reply to comment #8)
> (In reply to comment #6)
> > But shouldn't -Wno-strict-aliasing suppress the warning?
>
> Yes if you actually have -Wno-strict-aliasing after -Wall.
Andrew, note that this is not longer tru
--- Comment #9 from manu at gcc dot gnu dot org 2008-01-28 10:45 ---
Christoph, we need a testcase to be able to reproduce the bug, otherwise, we
cannot fix it.
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #8 from pinskia at gcc dot gnu dot org 2008-01-26 12:11 ---
(In reply to comment #6)
> But shouldn't -Wno-strict-aliasing suppress the warning?
Yes if you actually have -Wno-strict-aliasing after -Wall.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34973
--- Comment #7 from rguenth at gcc dot gnu dot org 2008-01-26 11:37 ---
Well, yes. Which is why a testcase would be nice (like preprocessed source of
one file you see this error).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34973
--- Comment #6 from Christoph_vW at reactos dot org 2008-01-26 09:51
---
I changed -Fno-strict-aliasing to -fno-strict-aliasing and the warning
disappeared.
But shouldn't -Wno-strict-aliasing suppress the warning?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34973
--- Comment #5 from pinskia at gcc dot gnu dot org 2008-01-25 22:13 ---
This is not a regression ...
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
16 matches
Mail list logo
