[Bug lto/50687] Missing symbols with -flto -fvisibility=hidden on 4.6.x but not on 4.7.0

2011-10-11 Thread lat at cern dot ch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50687 Lassi Tuura lat at cern dot ch changed: What|Removed |Added CC||lat at cern dot ch

[Bug lto/50687] Missing symbols with -flto -fvisibility=hidden on 4.6.x but not on 4.7.0

2011-10-11 Thread lat at cern dot ch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50687 --- Comment #4 from Lassi Tuura lat at cern dot ch 2011-10-11 12:00:47 UTC --- Right, as far as I can tell at the moment visibility option is somewhat peripheral to the issue. The main difference you see with LTO vs. no LTO appears to be whether

[Bug lto/48384] lto, linker-plugin and optimization clutter the stack trace

2011-05-14 Thread lat at cern dot ch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48384 Lassi Tuura lat at cern dot ch changed: What|Removed |Added CC||lat at cern dot ch

[Bug c/48597] x86-64 unwind register save location misses half-register write?

2011-04-14 Thread lat at cern dot ch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48597 --- Comment #1 from lat at cern dot ch 2011-04-14 07:53:27 UTC --- For completeness I didn't look for unwind inaccuracies with half-register writes other than the exact form (v)movd %xmmN,%ebp. It's entirely possible this bug happens only

[Bug middle-end/48597] x86-64 unwind register save location misses half-register write?

2011-04-14 Thread lat at cern dot ch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48597 --- Comment #8 from Lassi Tuura lat at cern dot ch 2011-04-15 05:40:33 UTC --- I confirm glibc 2.13 built with gcc 4.6.1 20110408 snapshot patched with gcc46-pr48597.patch results in correct unwind info for __ieee754_lgammaf_r. I checked all

[Bug c/48597] New: x86-64 unwind register save location misses half-register write?

2011-04-13 Thread lat at cern dot ch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48597 Summary: x86-64 unwind register save location misses half-register write? Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/43498] New: -fasynchronous-unwind-tables does not seem to do anything

2010-03-23 Thread lat at cern dot ch
Product: gcc Version: 4.3.4 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: lat at cern dot ch GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet

[Bug c++/43498] -fasynchronous-unwind-tables does not seem to do anything

2010-03-23 Thread lat at cern dot ch
--- Comment #2 from lat at cern dot ch 2010-03-23 18:52 --- Created an attachment (id=20174) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20174action=view) Random C source file for testing Random C source file for additional testing. Compile on Linux with and without

[Bug c++/43498] -fasynchronous-unwind-tables does not seem to do anything

2010-03-23 Thread lat at cern dot ch
--- Comment #3 from lat at cern dot ch 2010-03-23 18:54 --- Ah, that would explain it. Does it mean that all omissions and inaccuracies in unwind information are bugs? Like the lack of unwind info for thunks? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43498

[Bug middle-end/43498] -fasynchronous-unwind-tables does not seem to do anything

2010-03-23 Thread lat at cern dot ch
--- Comment #5 from lat at cern dot ch 2010-03-23 18:58 --- OK, reopening bug then. -- lat at cern dot ch changed: What|Removed |Added Status|RESOLVED

[Bug middle-end/43498] No unwind info for thunks even with -fasynchronous-unwind-tables

2010-03-23 Thread lat at cern dot ch
--- Comment #6 from lat at cern dot ch 2010-03-23 19:04 --- Changing subject to be more descriptive of the actual bug. -- lat at cern dot ch changed: What|Removed |Added