I have recently seen two GNU binutils/GNU ABI extensions on binutils@sourceware.org
They may potentially affect LLD and LLVM binary utilities, so I bring them
to your attention:)
(1) "dependency list for static libraries "
This adds a special member __.LIBDEP to an archive to represent
something similar to DT_NEEDED in a shared object.
This currently affects ar. ld is supposed to be affected but there is
no patch yet. This may affect llvm-ar and LLD.
(2) "[PATCH] Support SHF_GNU_RETAIN ELF section flag" and
"[PATCH v2] Support for SHF_GNU_RETAIN ELF Section Flag"
Basically, add a new section flag from SHF_MASKOS bits to express that
a section has GC root semantics (ld --gc-sections).
People mentioned GCC __attribute__((used)) could use this and the
author appears to be working on it (but a reply says that the frontend
feature do not need to hold up this proposal, so there is risk that it
is committed before the design is done).
This may affect Clang, LLVM's integrated assembler and LLD.
I have one reply at [PATCH v2] Support for SHF_GNU_RETAIN ELF Section Flag
(main points: (a) there are several alternative forms, e.g. SHT_GROUP, a
new SHT_* for GC root (b) the way they design the new section flag
adds one exception to "gas: error for section type, attr, or entsize
change")
Many people may not be subscribed to binutils@sourceware.org
If you want to reply with proper In-Reply-To: , you can get Message-ID:
from https://sourceware.org/pipermail/binutils/2020-September.txt.gz
Though I think you may simply reply with Re: $original_subject
I have recently seen two GNU binutils/GNU ABI extensions on binutils@sourceware.org
They may potentially affect LLD and LLVM binary utilities, so I bring them
to your attention:)
(1) "dependency list for static libraries "
This adds a special member __.LIBDEP to an archive to represent
something similar to DT_NEEDED in a shared object.
This currently affects ar. ld is supposed to be affected but there is
no patch yet. This may affect llvm-ar and LLD.
The next step is a GNU ld change. If some packages start to adopt the feature,
it can impose some compatibility burden on llvm-ar and LLD as well. If you want
to comment on the thread "dependency list for static libraries"
([PATCH] dependency list for static libraries), you can
use this tag:
(2) "[PATCH] Support SHF_GNU_RETAIN ELF section flag" and
"[PATCH v2] Support for SHF_GNU_RETAIN ELF Section Flag"
Basically, add a new section flag from SHF_MASKOS bits to express that
a section has GC root semantics (ld --gc-sections).
People mentioned GCC __attribute__((used)) could use this and the
author appears to be working on it (but a reply says that the frontend
feature do not need to hold up this proposal, so there is risk that it
is committed before the design is done).
This may affect Clang, LLVM's integrated assembler and LLD.
I have one reply at [PATCH v2] Support for SHF_GNU_RETAIN ELF Section Flag
(main points: (a) there are several alternative forms, e.g. SHT_GROUP, a
new SHT_* for GC root (b) the way they design the new section flag
adds one exception to "gas: error for section type, attr, or entsize
change")
This appears to receive good feedback and is likely to be accepted in GNU as
and ld. I personally have no issue with supporting it in LLVM's integrated
assembler and LLD.