public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagercon.com>
To: Neal Frager <neal.frager@amd.com>, binutils@sourceware.org
Cc: ibai.erkiaga-elorza@amd.com, nagaraju.mekala@amd.com,
	mark.hatle@amd.com, sadanand.mutyala@amd.com,
	appa.rao.nali@amd.com, vidhumouli.hunsigida@amd.com,
	luca.ceresoli@bootlin.com
Subject: Re: [PATCH v1 1/1] ld: microblaze: ignore rwx segments
Date: Wed, 4 Oct 2023 08:39:49 -0700	[thread overview]
Message-ID: <856b0724-a628-3571-1773-e3327eca8c04@eagercon.com> (raw)
In-Reply-To: <20230928055737.2306715-1-neal.frager@amd.com>

On 9/27/23 22:57, Neal Frager via Binutils wrote:
> The linker will generate warnings if it is creating an executable
> stack or a segment with all three read, write and execute permissions.
> These settings are not appropriate for all targets including
> MicroBlaze.
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
>   ld/configure.tgt | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/ld/configure.tgt b/ld/configure.tgt
> index ff0aaaae257..3aa595ef130 100644
> --- a/ld/configure.tgt
> +++ b/ld/configure.tgt
> @@ -55,6 +55,7 @@ if test "${ac_default_ld_warn_rwx_segments}" = unset; then
>       cris-*-* | crisv32-*-* | \
>       hppa*-*-* | \
>       mips*-*-* | \
> +    microblaze*-*-* | \
>       sparc*-*-* | \
>       v850*-*-*)
>         ac_default_ld_warn_rwx_segments=0

Committed.

-- 
Michael Eager


      reply	other threads:[~2023-10-04 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28  5:57 Neal Frager
2023-10-04 15:39 ` Michael Eager [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=856b0724-a628-3571-1773-e3327eca8c04@eagercon.com \
    --to=eager@eagercon.com \
    --cc=appa.rao.nali@amd.com \
    --cc=binutils@sourceware.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=mark.hatle@amd.com \
    --cc=nagaraju.mekala@amd.com \
    --cc=neal.frager@amd.com \
    --cc=sadanand.mutyala@amd.com \
    --cc=vidhumouli.hunsigida@amd.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).