[Bug c++/33599] segfault in program compiled by g++ 4.2, corrupted reference

[jacob at math dot jussieu dot fr]

------- Comment #4 from jacob at math dot jussieu dot fr  2007-09-30 13:47 -------
I had tried to make a shorter testcase but didn't find any that caused a crash.

But yes, the shorter testcase that you found indeed causes a crash here. With
both 4.1 and 4.2.

So indeed, that's probably a bug in my own code, and at least it's not a
regression from 4.1 to 4.2.

Thanks for your help and sorry for the false alert!

While I'm there, I'd like to draw your attention on the following fact. As I
said, with my library's benchmark, 4.2 produces much faster code than 4.1. But
trunk produces slower code than 4.2 does (almost as slow as 4.1). Is this
normal, given that this is a development version? Or is that a regression worth
reporting a bug against trunk/4.3 ?

More precisely, here are the execution times of our benchmark with various
versions of g++:
g++-4.1: 21s
g++-4.2: 4s
g++-4.3: 15s (8s with -fforce-addr)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33599