[Bug c++/16027] Enabling optimisation causes segfault

[s_gccbugzilla at nedprod dot com]

------- Additional Comments From s_gccbugzilla at nedprod dot com  2004-06-16 21:53 -------
(In reply to comment #5)
> Basically the problem is that the default allocator is not defined with your 
allocation scheme so this is 
> not a bug, optimization has nothing to do with except maybe something gets 
inlined.

Defining GLIBCXX_FORCE_NEW should prevent this. And doesn't -finline-functions 
work even with -O0?

(In reply to comment #3)
> What we would need is a complete bug report with repeatable testcase. 
> Please review 
>   http://gcc.gnu.org/bugs.html 
> for what we need. 

Yes but I'm facing over 30,000 lines and I don't know where to begin looking. I 
already tried a simple test case but it works fine. If I had some idea - eg; is 
it one of the i386 model optimisations? Why would GCC use one global operator 
new in one place and another elsewhere? BTW, the operator new's are weakly 
defined.

If it works on ICC with the SGI STL then it's pretty sure GCC is the culprit. 
This still wouldn't help me to narrow down the cause into a small testcase :(

Cheers,
Niall


-- 


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