[PATCH v1 1/4] Add target compile definitions in libraries interacting with DWARF arch-extensions
Hans-Peter Nilsson
hp@bitrange.com
Thu Dec 12 01:32:15 GMT 2024
Comfortably sniping from the sideline:
On Wed, 11 Dec 2024, Matthieu Longo wrote:
> DWARF 5 standard provides a space for vendor-specific DWARF directives.
> Binutils currently defines GNU-specific DWARF directives and vendor-specific
> ones for AArch64, SGI/MIPS, and Sparc architectures.
>
> However, the current implementation does not provide a "switch mechanism"
> to enable/disable those extensions depending on the selected target
> except in gas via TC_<arch>.
But that kind of ifdeffery is not a good template to follow, is
it? Gas can get away with it, because you can't really create a
multi-ISA assembler (not counting flavors within each of e.g.
"intel" and "arm" families as different).
Honestly, when doing this larger level of work, why not create
such a mechanism, one that would even work with
--enable-targets=all?
brgds, H-P
More information about the Binutils
mailing list