This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/33599] segfault in program compiled by g++ 4.2, corrupted reference
- From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Sep 2007 16:05:11 -0000
- Subject: [Bug c++/33599] segfault in program compiled by g++ 4.2, corrupted reference
- References: <bug-33599-13749@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from rguenth at gcc dot gnu dot org 2007-09-30 16:05 -------
Well, the speed regression is certainly not welcome. So, if you have a
testcase
that shows this you might want to open a new bugreport. A plus, if you can
identify the single(?) hot loop that executes slower and compare assembler
output for it - maybe there's something obvious.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33599