[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/26404] ld: INSERT [AFTER|BEFORE] variant for extension purposes
From: |
nickc at redhat dot com |
Subject: |
[Bug ld/26404] ld: INSERT [AFTER|BEFORE] variant for extension purposes |
Date: |
Thu, 17 Sep 2020 15:53:58 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=26404
--- Comment #4 from Nick Clifton <nickc at redhat dot com> ---
(In reply to Peter Smith from comment #3)
> As I understand it [*] just adding the script on the command line but
> without the -T or --script will cause the linker to merge without the need
> for INSERT etc.
You are right. (I had thought that the fragment would override the
built-in script where there are conflicts, but it appears that it
augments it instead).
So maybe what we need are *two* new command line options, just to make
things clear: --augment-script=<name> and --overwrite-script=<name>.
Hmm, maybe this is going too far. We already have -t/--script, so
how about we just add --script-action=[replace|merge|overwrite|new] ?
So --script-action=replace would mean that --script replaces the built-in
script, as it does at the moment. --script-action=merge would mean
that --script would behave like script fragments do at the moment, and
augment the built-in script. --script-action=overwrite would mean
the same, except that where there are multiple definitions of the same
section, the definition in the script replaces the definition in the
built-in. --script-action=new means that only new definitions can be
added and an error is generated if there are any conflicts.
--
You are receiving this mail because:
You are on the CC list for the bug.