This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/39015] [4.3 regression] wrong code building libgsf
- From: "sje at cup dot hp dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Jan 2009 18:57:12 -0000
- Subject: [Bug middle-end/39015] [4.3 regression] wrong code building libgsf
- References: <bug-39015-11764@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #9 from sje at cup dot hp dot com 2009-01-29 18:57 -------
So far I have been unable to reproduce this problem. When compiling gsf-scan.i
I do not even reach the code that I changed in PR 38615 and I get the same code
with or without my change included.
Assuming there is a way to trigger this, I wonder if the program is legal. In
particular I was looking at the initialization of GbArgTable which has a lot of
holes in it. If the optimization affects whether or not these holes get set to
zero and if the program is accessing these uninitialized locations that could
cause a change in behaviour.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39015