From: Nick Alcock <nick.alcock@oracle.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: genscripts comment tidy
Date: Wed, 16 Oct 2019 14:10:00 -0000 [thread overview]
Message-ID: <87a7a0aiiu.fsf@esperi.org.uk> (raw)
In-Reply-To: <20191016003312.GW10114@bubble.grove.modra.org> (Alan Modra's message of "Wed, 16 Oct 2019 11:03:12 +1030")
On 16 Oct 2019, Alan Modra spake thusly:
> -# A .x script file is the default script.
> -# A .xr script is for linking without relocation (-r flag).
> -# A .xu script is like .xr, but *do* create constructors (-Ur flag).
> -# A .xn script is for linking with -n flag (mix text and data on same page).
> -# A .xbn script is for linking with -N flag (mix text and data on same page).
> -# A .xs script is for generating a shared library with the --shared
> -# flag; it is only generated if $GENERATE_SHLIB_SCRIPT is set by the
> -# emulation parameters.
> -# A .xc script is for linking with -z combreloc; it is only generated if
> -# $GENERATE_COMBRELOC_SCRIPT is set by the emulation parameters or
> -# $SCRIPT_NAME is "elf".
> -# A .xsc script is for linking with --shared -z combreloc; it is generated
> -# if $GENERATE_COMBRELOC_SCRIPT is set by the emulation parameters or
> -# $SCRIPT_NAME is "elf" and $GENERATE_SHLIB_SCRIPT is set by the emulation
> -# parameters too.
Is this stuff still documented anywhere after this commit? Because I
know I found this specific comment very useful only a month ago, and the
purpose of the differently suffixed linker scripts is otherwise quite opaque.
next prev parent reply other threads:[~2019-10-16 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 0:33 Alan Modra
2019-10-16 14:10 ` Nick Alcock [this message]
2019-10-16 14:16 ` Nick Clifton
2019-10-16 18:18 ` Nick Alcock
2020-05-31 12:42 ` ld CTF deduplicator should be coming fairly soon (was Re: genscripts comment tidy) Nick Alcock
2020-05-31 17:10 ` Fangrui Song
2019-10-16 23:47 ` genscripts comment tidy Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7a0aiiu.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).