This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/29818] code with SSE segfaults with gcc-3.4.6, runs fine with gcc-4.1.1



------- Comment #5 from sergstesh at yahoo dot com  2006-11-14 01:36 -------
(In reply to comment #4)
> (In reply to comment #3)
> > I am developing pretty heavy SSE-based code, and performance-wise gcc-3.4.6 is
> > the best so far. Sorry, I cant' post the code, but here are performance
> > figures (output of 'time' command):
> 
> Then, you are not helping the project: a closed branch is not re-opened because
> of a bug and posting performance numbers without a *reduced* snippet
> pinpointing the specific issue is not useful to the developers (the only
> possible effect is making someone slightly nervous ;)
> 

The "real" piece of code I'm working on is 14923 lines long (the "C" file, not
the "i" file). I can think of obfuscating it to the point it becomes not clear
what it is doing functionally.

We can make a deal: I obfuscate and publish the code, you guys fix the
bug preserving, if possible, performance.

The code is really complex, and it's not realistic for me to make it smaller.

By the way, using gcc-3.4.6 with '-O3' makes performance much worse, worse
than the one obtained with gcc-4.1.1.

On the other hand, '-O3' applied to gcc-4.1.1 does not change the performance
that drastic, though I do not remember at the moment whether the performance
improves or deteriorates.


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]