[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-08-10 Thread pluto at agmk dot net
--- Comment #13 from pluto at agmk dot net 2006-08-10 09:58 --- in fact it was a gcc bug. gcc version 4.1.2 20060530 gives wrong code. gcc version 4.1.2 20060712 gives correct code. tree dump shows that gcc-20060530 removes some parts [*] of vector_base initialization and finally

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-08-10 Thread pluto at agmk dot net
--- Comment #14 from pluto at agmk dot net 2006-08-10 09:58 --- fixed on current 4.1 branch. -- pluto at agmk dot net changed: What|Removed |Added

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-05-10 Thread pluto at agmk dot net
--- Comment #12 from pluto at agmk dot net 2006-05-10 22:36 --- following reduced testcase works with libstdc++ and segv with stlport. #include list #include vector struct A { }; int main() { std::list A* l; std::vector A* v( l.end(), l.end() ); return 0; }

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-05-03 Thread pluto at agmk dot net
--- Comment #8 from pluto at agmk dot net 2006-05-03 09:02 --- Created an attachment (id=11364) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11364action=view) full 32-bit testcase. -- pluto at agmk dot net changed: What|Removed |Added

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-05-03 Thread pluto at agmk dot net
--- Comment #9 from pluto at agmk dot net 2006-05-03 09:05 --- (In reply to comment #7) The testcase works for me as I don't have the STLport installed (and what is in this bug is not enough to reproduce the bug). so, try latest testcase. $ make g++ testDrv.ii -o testDrv

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-05-03 Thread pluto at agmk dot net
--- Comment #10 from pluto at agmk dot net 2006-05-03 09:19 --- Created an attachment (id=11365) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11365action=view) source code -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27156

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-05-03 Thread pluto at agmk dot net
--- Comment #11 from pluto at agmk dot net 2006-05-03 09:22 --- also fails on 64-bit system. $ g++ testDrv.cpp -o testDrv -pthread -O2 \ -I/usr/include/stlport -nodefaultlibs -lstlport -lc $ ./testDrv *** glibc detected *** ./testDrv: munmap_chunk():

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-04-30 Thread pinskia at gcc dot gnu dot org
--- Comment #7 from pinskia at gcc dot gnu dot org 2006-04-30 08:02 --- The testcase works for me as I don't have the STLport installed (and what is in this bug is not enough to reproduce the bug). -- pinskia at gcc dot gnu dot org changed: What|Removed

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-04-19 Thread pluto at agmk dot net
--- Comment #4 from pluto at agmk dot net 2006-04-19 08:12 --- (In reply to comment #2) Well this works with just compiling like: g++ -O2 -pthread t.ii With 4.1.0 (4.1.0 20051026). Yes, it works with libstdcxx but the testcase uses STLport-5.0.2. --

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-04-19 Thread pluto at agmk dot net
--- Comment #5 from pluto at agmk dot net 2006-04-19 08:33 --- (In reply to comment #3) Are you sure that you are not mixing operator new and deletes up so the stlport's operator delete is being called on memory allocated from operator new from libstdc++? STLport uses

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-04-19 Thread pluto at agmk dot net
--- Comment #6 from pluto at agmk dot net 2006-04-19 08:38 --- It works also with 4.1.x -fstrict-aliasing -fno-inline. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27156

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-04-18 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-04-19 00:36 --- Well this works with just compiling like: g++ -O2 -pthread t.ii With 4.1.0 (4.1.0 20051026). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27156

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-04-18 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-04-19 00:38 --- Are you sure that you are not mixing operator new and deletes up so the stlport's operator delete is being called on memory allocated from operator new from libstdc++? Also is there a reason why you are using

[Bug other/27156] SIGSEGV in operator delete() / wrong-code?

2006-04-14 Thread pluto at agmk dot net
--- Comment #1 from pluto at agmk dot net 2006-04-14 09:36 --- Created an attachment (id=11265) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11265action=view) preprocessed source (compiled with stlport-5.0.2) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27156