From: Matthias Klose <doko@ubuntu.com>
To: Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org, YunQiang Su <syq@debian.org>
Cc: "debian-mips@lists.debian.org" <debian-mips@lists.debian.org>
Subject: Re: Getting ready for the 2.39 branch/release
Date: Thu, 23 Jun 2022 15:07:46 +0200 [thread overview]
Message-ID: <4a62e7f8-08a2-6bf1-b1e6-6a834199dec9@ubuntu.com> (raw)
In-Reply-To: <98f2210a-9115-1607-2828-fc9c7c4a1477@redhat.com>
On 23.06.22 12:07, Nick Clifton wrote:
> 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 ?
No, not yet.
> Would the attached patch solve the problem ?
did you want to set ac_default_ld_warn_rwx_segments in the second chunk?
> 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 ?
I had asked a mips porter, no reply yet.
Matthias
next prev parent reply other threads:[~2022-06-23 13:08 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
2022-06-23 13:07 ` Matthias Klose [this message]
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=4a62e7f8-08a2-6bf1-b1e6-6a834199dec9@ubuntu.com \
--to=doko@ubuntu.com \
--cc=binutils@sourceware.org \
--cc=debian-mips@lists.debian.org \
--cc=nickc@redhat.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).