From: Alan Modra <amodra@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: libffi-discuss@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix up libffi linux64*.S for ppc32-linux
Date: Thu, 11 Sep 2014 00:12:00 -0000 [thread overview]
Message-ID: <20140911001225.GW17693@bubble.grove.modra.org> (raw)
In-Reply-To: <20140910144833.GJ17454@tucnak.redhat.com>
On Wed, Sep 10, 2014 at 04:48:33PM +0200, Jakub Jelinek wrote:
> * src/powerpc/linux64.S: Emit .note.GNU-stack even when
> POWERPC64 is not defined.
> * src/powerpc/linux64_closure.S: Likewise. Also test _CALL_ELF == 2.
Looks reasononable to me, and oops, I think I introduced this problem
when adding ELFv2 support by moving those notes.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2014-09-11 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 14:48 Jakub Jelinek
2014-09-11 0:12 ` Alan Modra [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=20140911001225.GW17693@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=libffi-discuss@sourceware.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).