[PATCH 3/4] ELF: SHF_STRINGS isn't really tied to SHF_MERGE

[Jan Beulich]

On 17.01.2025 12:13, H.J. Lu wrote:
> It is very undesirable to require changing existing assembly codes
> in the real world.  We shouldn't make such assembler changes.
> It may be OK for the assembler to issue a warning.  But it should
> keep generating correct and working object files.

With "working" then meaning something other than "being spec compliant"?
Any consumer may legitimately expect spec compliant objects, and error
out otherwise. What we did produce before wasn't spec compliant, and
hence according to my reading not "working". Something needs to be done
about situations like this; it's wrong to leave tools broken just
because they have always been broken. It's merely a matter of determining
which of perhaps multiple possible approaches may cause the least
fallout. All I can do here is encourage people to pay more attention to
patches being posted.

Jan