From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] Move new features above the 'Changes in 2.41' comment
Date: Fri, 10 Nov 2023 10:21:40 +0000 (GMT) [thread overview]
Message-ID: <20231110102140.E388D3858D32@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a73c0d9b228cb11d4dd9c045c692229ff6b7b06a
commit a73c0d9b228cb11d4dd9c045c692229ff6b7b06a
Author: Nick Clifton <nickc@redhat.com>
Date: Fri Nov 10 10:21:34 2023 +0000
Move new features above the 'Changes in 2.41' comment
Diff:
---
ld/NEWS | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/ld/NEWS b/ld/NEWS
index 34a2e14fe1b..73eb253b798 100644
--- a/ld/NEWS
+++ b/ld/NEWS
@@ -1,9 +1,13 @@
-*- text -*-
-Changes in 2.41:
-
* Add support for the KVX instruction set.
+* A new linker script sorting directive has been added: REVERSE. This reverses
+ the order of the sorting. It may be combined with either SORT_BY_NAME or
+ SORT_BY_INIT_PRIORITY.
+
+Changes in 2.41:
+
* The linker now accepts a command line option of --remap-inputs
<PATTERN>=<FILE> to relace any input file that matches <PATTERN> with
<FILE>. In addition the option --remap-inputs-file=<FILE> can be used to
@@ -12,10 +16,6 @@ Changes in 2.41:
* The linker command line option --print-map-locals can be used to include
local symbols in a linker map. (ELF targets only).
-* A new linker script sorting directive has been added: REVERSE. This reverses
- the order of the sorting. It may be combined with either SORT_BY_NAME or
- SORT_BY_INIT_PRIORITY.
-
* For most ELF based targets, if the --enable-linker-version option is used
then the version of the linker will be inserted as a string into the .comment
section.
reply other threads:[~2023-11-10 10:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231110102140.E388D3858D32@sourceware.org \
--to=nickc@sourceware.org \
--cc=bfd-cvs@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).