From: Jeff Law <jeffreyalaw@gmail.com>
To: Stafford Horne <shorne@gmail.com>
Cc: GCC patches <gcc-patches@gcc.gnu.org>,
Linux OpenRISC <linux-openrisc@vger.kernel.org>
Subject: Re: [PATCH] or1k: add .note.GNU-stack section on linux
Date: Mon, 6 Jan 2025 10:03:50 -0700 [thread overview]
Message-ID: <cbc35acb-968b-4c98-902b-fea85a175808@gmail.com> (raw)
In-Reply-To: <Z3wMiWSBG7BJyYSv@antec>
On 1/6/25 10:02 AM, Stafford Horne wrote:
> On Mon, Jan 06, 2025 at 07:37:56AM -0700, Jeff Law wrote:
>>
>>
>> On 1/6/25 6:01 AM, Stafford Horne wrote:
>>> In the OpenRISC build we get the following warning:
>>>
>>> ld: warning: __modsi3_s.o: missing .note.GNU-stack section implies executable stack
>>> ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
>>>
>>> Fix this by adding a .note.GNU-stack to indicate the stack does not need to be
>>> executable for the lib1funcs.
>>>
>>> Note, this is also needed for the upcoming glibc 2.41.
>>>
>>> libgcc/
>>> * config/or1k/lib1funcs.S: Add .note.GNU-stack section on linux.
>> OK for the trunk. You've got write privs, correct?
>
> Thanks,
>
> Yes I should still have access. Also, I would like to add to the release-14
> branch. Is there anything special I need to do to add the patch there?
Nothing really special on the release branches.
jeff
next prev parent reply other threads:[~2025-01-06 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 13:01 [PATCH] or1k: add .note.GNU-stack section on linux Stafford Horne
2025-01-06 14:37 ` Jeff Law
2025-01-06 17:02 ` Stafford Horne
2025-01-06 17:03 ` Jeff Law [this message]
2025-01-06 17:26 ` Stafford Horne
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=cbc35acb-968b-4c98-902b-fea85a175808@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=shorne@gmail.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 NNTP newsgroup(s).