[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-09-22 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 --- Comment #10 from cvs-commit at gcc dot gnu.org --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-08-15 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 Nick Clifton changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-08-13 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 Alan Modra changed: What|Removed |Added Status|ASSIGNED|NEW CC|

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-08-13 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 --- Comment #7 from cvs-commit at gcc dot gnu.org --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch,

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-08-13 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 Alan Modra changed: What|Removed |Added Status|NEW |ASSIGNED CC|amodra at gm

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-08-13 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 --- Comment #5 from Alan Modra --- I got that wrong. a.o and b.o appear in the correct order in the output .eh_frame. Apparently it is the elf-eh-frame.c code that sees them in reverse order. -- You are receiving this mail because: You are

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-08-13 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 --- Comment #4 from Alan Modra --- There are a couple of things going on here, but the "Invalid CIE pointer" is a readelf bug I'd say. There's nothing prohibiting a FDE to be located before its CIE. The .eh_frame cie_id is a signed relative

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-08-12 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 --- Comment #3 from Nick Clifton --- The first test case no longer reproduces the problem - but the problem itself still exists. I have now uploaded a second test case that still demonstrates the problem. -- You are receiving this mail beca

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-08-12 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 Nick Clifton changed: What|Removed |Added Attachment #7405|0 |1 is obsolete|

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-07-27 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 Alan Modra changed: What|Removed |Added CC||amodra at gmail dot com --- Comment #1 f

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-02-12 Thread law at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 law at redhat dot com changed: What|Removed |Added CC||law at redhat dot com -- You

[Bug ld/16563] Corrupt .eh-frame section created when linking LTO and non-LTO objects

2014-02-12 Thread polacek at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=16563 Marek Polacek changed: What|Removed |Added CC||polacek at redhat dot com -- You are