[Bug gas/32022] Assembler shouldn't accept invalid TLS instructions

[jbeulich at suse dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=32022

Jan Beulich <jbeulich at suse dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jbeulich at suse dot com

--- Comment #5 from Jan Beulich <jbeulich at suse dot com> ---
(In reply to H.J. Lu from comment #0)
> [hjl@gnu-tgl-3 tmp]$ ld y.o
> ld: warning: cannot find entry symbol _start; defaulting to 0000000000401000
> ld: y.o: TLS transition from R_X86_64_GOTTPOFF to R_X86_64_TPOFF32 against
> `foo' at 0x3 in section `.text' failed
> ld: final link failed: bad value

And why exactly does linking need to fail is such a situation? The TLS
transitions are optional, aren't they? Not being able to do carry one out may
indeed deserve a warning (with a control to silence), but not more.

(In reply to H.J. Lu from comment #1)
> An assembler option should be provided to control the behavior.

Having an option to control this is fine with me. Yet then, if enabled, it
should really diagnose all suspicious constructs, not just a (random) subset.

-- 
You are receiving this mail because:
You are on the CC list for the bug.