Consider using GCC DevKit build with --enable-linker-build-id

[andrew-m-leonard]

GCC with ELF and Binutils supports generation of "build-id" sections for additional debugging information for use when using separate debuginfo: https://sourceware.org/gdb/current/onlinedocs/gdb.html/Separate-Debug-Files.html

Consider whether the Adoptium GCC DevKit build should use --enable-linker-build-id

[jerboaa]

From the gnu linker man page:

--build-id
--build-id=style
    Request creation of ".note.gnu.build-id" ELF note section. The contents of the note are unique bits identifying this linked file. style can be "uuid" to use 128 random bits, "sha1" to use a 160-bit SHA1 hash on the normative parts of the output contents, "md5" to use a 128-bit MD5 hash on the normative parts of the output contents, or "0x hexstring " to use a chosen bit string specified as an even number of hexadecimal digits ("-" and ":" characters between digit pairs are ignored). If style is omitted, "sha1" is used.

    The "md5" and "sha1" styles produces an identifier that is always the same in an identical output file, but will be unique among all nonidentical output files. It is not intended to be compared as a checksum for the file's contents. A linked file may be changed later by other tools, but the build ID bit string identifying the original linked file does not change.

    Passing "none" for style disables the setting from any "--build-id" options earlier on the command line. 

[jerboaa]

Specifically this:

The "md5" and "sha1" styles produces an identifier that is always the same in an identical output file.

[jerboaa]

Two random builds don't produce identical build-id's for libjvm.so (for builds without any of the reproducible build options) on Linux.