From: Nick Clifton <nickc@redhat.com>
To: Matthias Klose <doko@ubuntu.com>,
binutils@sourceware.org, YunQiang Su <syq@debian.org>
Subject: Re: Getting ready for the 2.39 branch/release
Date: Thu, 23 Jun 2022 11:07:34 +0100 [thread overview]
Message-ID: <98f2210a-9115-1607-2828-fc9c7c4a1477@redhat.com> (raw)
In-Reply-To: <69df0c2f-016d-96ed-b4c6-2537453cb3fa@ubuntu.com>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
Hi Matthias,
> Debian and Ubuntu are using the current trunk for the releases in development. There's currently one issue that I'm aware of:
>
> https://bugs.debian.org/1013244
Is there a corresponding binutils PR for this ?
Would the attached patch solve the problem ?
If the need for an executable stack is restricted to the hard-float ABI,
is there a way to determine this from the target configuration triplet ?
Is there an explanation somewhere of why the hard-float ABI needs an
executable stack - and possibly how this need might be removed ?
Cheers
Nick
[-- Attachment #2: p.patch --]
[-- Type: text/x-patch, Size: 1712 bytes --]
diff --git a/ld/configure b/ld/configure
index 95c21406b41..14311847b57 100755
--- a/ld/configure
+++ b/ld/configure
@@ -15465,6 +15465,8 @@ case "${target}" in
# The HPPA port needs to support older kernels that use executable stacks
# for signals and syscalls.
hppa*-*-*) ac_default_ld_warn_execstack=0 ;;
+ # Similarly for MIPS targets.
+ mips*-*-*) ac_default_ld_warn_execstack=0 ;;
*) ac_default_ld_warn_execstack=2 ;;
esac
# Check whether --enable-warn-execstack was given.
@@ -17281,6 +17283,8 @@ if test "${ac_default_ld_warn_rwx_segments}" = unset; then
# The HPPA's PLT section uses a constructed trampoline, hence it needs to
# have a RWX segment.
hppa*-*-*) ac_default_ld_warn_rwx_segments=0 ;;
+ # Similarly for MIPS targets.
+ mips*-*-*) ac_default_ld_warn_execstack=0 ;;
*) ac_default_ld_warn_rwx_segments=1 ;;
esac
fi
diff --git a/ld/configure.ac b/ld/configure.ac
index d587c46cc51..fc8b94c9290 100644
--- a/ld/configure.ac
+++ b/ld/configure.ac
@@ -210,6 +210,8 @@ esac])
# The HPPA port needs to support older kernels that use executable stacks
# for signals and syscalls.
hppa*-*-*) ac_default_ld_warn_execstack=0 ;;
+ # Similarly for MIPS targets.
+ mips*-*-*) ac_default_ld_warn_execstack=0 ;;
*) ac_default_ld_warn_execstack=2 ;;
esac]
AC_ARG_ENABLE(warn-execstack,
@@ -573,6 +575,8 @@ if test "${ac_default_ld_warn_rwx_segments}" = unset; then
# The HPPA's PLT section uses a constructed trampoline, hence it needs to
# have a RWX segment.
hppa*-*-*) ac_default_ld_warn_rwx_segments=0 ;;
+ # Similarly for MIPS targets.
+ mips*-*-*) ac_default_ld_warn_execstack=0 ;;
*) ac_default_ld_warn_rwx_segments=1 ;;
esac]
fi
next prev parent reply other threads:[~2022-06-23 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 11:09 Nick Clifton
2022-06-22 6:36 ` Jan Beulich
2022-06-22 19:35 ` Matthias Klose
2022-06-22 23:00 ` Vladimir Mezentsev
2022-06-23 12:50 ` Matthias Klose
2022-06-23 10:07 ` Nick Clifton [this message]
2022-06-23 13:07 ` Matthias Klose
2022-06-23 15:43 ` Nick Clifton
2022-06-23 23:02 ` Hans-Peter Nilsson
2022-06-24 10:01 ` Nick Clifton
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=98f2210a-9115-1607-2828-fc9c7c4a1477@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=doko@ubuntu.com \
--cc=syq@debian.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).