[Bug lto/65015] LTO produces randomly ordered debug information

[conchur at web dot de]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015

conchur at web dot de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #34724|0                           |1
        is obsolete|                            |

--- Comment #9 from conchur at web dot de ---
Created attachment 34746
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34746&action=edit
Mini Testcases

Thanks a lot. I was playing around with your new patches. And I was looking at
the buildid the whole time (assuming that it is the hash over the whole
binary). This doesn't seem to be and was therefore a wrong assumption by me.

What does it mean:

 * your patches work fine with -flto -flto-partition=none (which is awesome)
 * my conclusion that it also works with plain -flto as I said in the Debian
bug #777753 was wrong

The testcases are updated to reflect this.


SIMPLE-COMPILE: OK
SIMPLE-LINK: OK
LTO-LINK: FAIL
LTO-OBJDUMP: FAIL
LTO-EXTERNAL-DEBUG: FAIL
LTO-STRIP-LINK: FAIL
LTO-STRIP-EXTERNAL-DEBUG: FAIL
LTO-BUILDID-LINK: FAIL
LTO-SAVETEMPS-LINK: FAIL
LTO-SAVETEMPS-EXTERNAL-DEBUG: FAIL
NOPART-LTO-LINK: OK
NOPART-LTO-OBJDUMP: OK
NOPART-LTO-EXTERNAL-DEBUG: OK
NOPART-LTO-STRIP-LINK: OK
NOPART-LTO-STRIP-EXTERNAL-DEBUG: OK
NOPART-LTO-BUILDID-LINK: OK
NOPART-LTO-SAVETEMPS-LINK: OK
NOPART-LTO-SAVETEMPS-EXTERNAL-DEBUG: OK