From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Nicholas Piggin <npiggin@gmail•com>
Cc: linuxppc-dev@lists•ozlabs.org, Alan Modra <amodra@gmail•com>
Subject: Re: [2/3] powerpc: allow compilation on cross-endian toolchain
Date: Wed, 8 Mar 2017 18:25:46 +1100 (AEDT) [thread overview]
Message-ID: <3vdQ6f4vgvz9sN5@ozlabs.org> (raw)
In-Reply-To: <20161127134620.74007843@roar.ozlabs.ibm.com>
On Sun, 2016-11-27 at 02:46:20 UTC, Nicholas Piggin wrote:
> Subject: [PATCH] powerpc: allow compilation on cross-endian toolchain
>
> GCC can compile with either endian, but the ABI version always
> defaults to the default endian. Alan Modra says:
>
> you need both -mbig and -mabi=elfv1 to make a powerpc64le gcc
> generate powerpc64 code
>
> The opposite is true for powerpc64 when generating -mlittle it
> requires -mabi=elfv2 to generate v2 ABI. This change adds ABI
> annotations together with endianness. The kernel with ELFv2 ABI
> also uses -mcall-aixdesc, but boot/ does not.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail•com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/4dc831aa88132f835cefe876aa0206
cheers
next prev parent reply other threads:[~2017-03-08 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 13:02 [PATCH 0/3] minor build fixes Nicholas Piggin
2016-11-23 13:02 ` [PATCH 1/3] powerpc/64e: convert cmpi to cmpwi in head_64.S Nicholas Piggin
2016-11-29 12:58 ` [1/3] " Michael Ellerman
2016-11-23 13:02 ` [PATCH 2/3] powerpc: allow compilation on cross-endian toolchain Nicholas Piggin
2016-11-24 9:04 ` Nicholas Piggin
2016-11-26 3:00 ` Nicholas Piggin
2016-11-26 7:30 ` Michael Ellerman
2016-11-27 2:46 ` Nicholas Piggin
2017-02-02 8:08 ` Naveen N. Rao
2017-03-08 7:25 ` Michael Ellerman [this message]
2016-11-23 13:02 ` [PATCH 3/3] powerpc/64e: don't branch to dot symbols Nicholas Piggin
2016-11-29 12:58 ` [3/3] " Michael Ellerman
2016-11-23 23:03 ` [PATCH 0/3] minor build fixes Alan Modra
2016-11-24 1:04 ` Nicholas Piggin
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=3vdQ6f4vgvz9sN5@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=amodra@gmail$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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