[Bug gold/14187] gold incorrectly requires hexadecimals to start with 0x with -Ttext/-Tdata/-Tbss

[ccoutant at gmail dot com]

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

--- Comment #14 from Cary Coutant <ccoutant at gmail dot com> ---
(In reply to Stas Sergeev from comment #13)
> (In reply to Cary Coutant from comment #11)
> > Created attachment 8557 [details]
> > Patch to fix gold to parse -Ttext, etc., options as hex numbers
> > The attached patch changes gold to parse the -Ttext, etc., values
> > as hex numbers, but will print a warning if it sees a value that
> > looks more like a decimal number (in order to catch legacy uses).
> Please don't.
> -Ttext in gold means entirely different thing, 0x won't help.
> Don't break you current users without fixing anything at all.

I don't see why we should leave this bug unfixed just because we don't match
Gnu ld's behavior for -Ttext.

The original report was about accepting hex numbers without the 0x, and had
nothing to do with what you're talking about.

Ian has already explained why Gnu ld's -Ttext is useless on ELF targets, and I
did a little historical research to find that the -Ttext option on several
other linkers is described it as setting the address of the text *segment*,
which is what gold implements.

I think if there's anyone out there using -Ttext with a decimal value, the
proposed patch will probably catch it and warn them of the change, assuming a
high likelihood that they're using a multiple of a power of two. It's probably
more likely that everyone is already spelling it with a 0x.

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