[Bug other/39979] possible wrong code at all -0x levels.

2010-04-18 Thread pluto at agmk dot net
--- Comment #3 from pluto at agmk dot net 2010-04-18 13:34 --- Created an attachment (id=20408) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20408action=view) some tree dumps from 4.3/4.5. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39979

[Bug other/39979] possible wrong code at all -0x levels.

2010-04-18 Thread pluto at agmk dot net
--- Comment #4 from pluto at agmk dot net 2010-04-18 13:44 --- during analysis the boost::thread::start_thread() function which causes invalid writes detected by valgrind i've noticed that gcc-4.5 generates bigger and more complex code of this function with few more lock'ed opcodes.

[Bug other/39979] possible wrong code at all -0x levels.

2010-04-18 Thread rguenth at gcc dot gnu dot org
--- Comment #5 from rguenth at gcc dot gnu dot org 2010-04-18 18:30 --- (In reply to comment #4) during analysis the boost::thread::start_thread() function which causes invalid writes detected by valgrind i've noticed that gcc-4.5 generates bigger and more complex code of this

[Bug other/39979] possible wrong code at all -0x levels.

2010-04-18 Thread pluto at agmk dot net
--- Comment #6 from pluto at agmk dot net 2010-04-18 19:01 --- Created an attachment (id=20413) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20413action=view) testcase.#0. -- pluto at agmk dot net changed: What|Removed |Added

[Bug other/39979] possible wrong code at all -0x levels.

2010-04-18 Thread pluto at agmk dot net
--- Comment #7 from pluto at agmk dot net 2010-04-18 19:04 --- (In reply to comment #5) (In reply to comment #4) during analysis the boost::thread::start_thread() function which causes invalid writes detected by valgrind i've noticed that gcc-4.5 generates bigger and more complex

[Bug other/39979] possible wrong code at all -0x levels.

2010-04-18 Thread pluto at agmk dot net
--- Comment #8 from pluto at agmk dot net 2010-04-18 20:28 --- debbuging 4.3 vs 4.5 start_thread() shows different results: 4.3: 182x void thread::start_thread() 183x { 184x thread_info-self=thread_info; 185tint const res =

[Bug other/39979] possible wrong code at all -0x levels.

2010-04-18 Thread rguenth at gcc dot gnu dot org
--- Comment #9 from rguenth at gcc dot gnu dot org 2010-04-18 20:32 --- (In reply to comment #8) debbuging 4.3 vs 4.5 start_thread() shows different results: 4.3: 182x void thread::start_thread() 183x { 184x thread_info-self=thread_info; 185tint const

[Bug other/39979] possible wrong code at all -0x levels.

2010-04-18 Thread rguenth at gcc dot gnu dot org
--- Comment #10 from rguenth at gcc dot gnu dot org 2010-04-18 20:33 --- Oh, and does it fail with http://gcc.gnu.org/bugzilla/attachment.cgi?id=20394 applied? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39979

[Bug other/39979] possible wrong code at all -0x levels.

2010-04-17 Thread pluto at agmk dot net
--- Comment #2 from pluto at agmk dot net 2010-04-17 13:58 --- ok, i've tested the boost-1.42.0 libs with the application and different compiler configuration (4.3/4.4/4.5) and now i'm sure that libboost-thread.a is broken by 4.4/4.5. i'll dump gcc trees from that library and compare