From: Nick Clifton <nickc@redhat.com>
To: Matthew Malcomson <matthew.malcomson@arm.com>, binutils@sourceware.org
Cc: Richard.Earnshaw@arm.com
Subject: Re: [PATCH] ld: aarch64: Update test linker scripts relocs.ld and relocs-ilp32.ld
Date: Fri, 29 Jul 2022 11:16:45 +0100 [thread overview]
Message-ID: <9a1563ee-2da3-3ecd-2a16-e76231dfd47f@redhat.com> (raw)
In-Reply-To: <8cb2b1e0-8b89-4aa1-8b03-92dbd57c98f9@AZ-NEU-EX03.Arm.com>
Hi Matthew,
> The updates are to ensure that the .data section exists. This means
> that we always have a data section. That means that we don't create a
> RWX segment and avoid the corresponding warning.
>
> We get this warning when testing aarch64-none-elf with -mcmodel=tiny.
> N.b. this changes quite a few testcases from fail to pass.
>
> OK for master?
Approved - please apply. (Sorry for the long delay in reviewing this patch).
Please also apply to the 2.39 branch.
Cheers
Nick
prev parent reply other threads:[~2022-07-29 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 12:43 Matthew Malcomson
2022-07-29 10:16 ` Nick Clifton [this message]
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=9a1563ee-2da3-3ecd-2a16-e76231dfd47f@redhat.com \
--to=nickc@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=matthew.malcomson@arm.com \
/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).