From: Alan Modra <amodra@bigpond.net.au>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Peter Bergner <bergner@vnet.ibm.com>,
Daniel Jacobowitz <drow@false.org>,
Thiago Jung Bauermann <bauerman@br.ibm.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [patch] Fix power7 ppc64 binaries loading
Date: Tue, 03 Mar 2009 23:48:00 -0000 [thread overview]
Message-ID: <20090303234833.GE9491@bubble.grove.modra.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0903032329050.15240@digraph.polyomino.org.uk>
On Tue, Mar 03, 2009 at 11:30:27PM +0000, Joseph S. Myers wrote:
> On Wed, 4 Mar 2009, Alan Modra wrote:
>
> > Google for E500 ABI. It should only be enabled when you are
> > assembling for e500. I've committed the following to mainline
> > and 2.19 branch.
> >
> > * config/tc-ppc.c (md_assemble): APUinfo only for e500.
>
> > - if (ppc_cpu & (PPC_OPCODE_SPE
> > - | PPC_OPCODE_ISEL | PPC_OPCODE_EFS
> > - | PPC_OPCODE_BRLOCK | PPC_OPCODE_PMR | PPC_OPCODE_CACHELCK
> > - | PPC_OPCODE_RFMCI))
> > + if ((ppc_cpu & PPC_OPCODE_E500MC) != 0)
>
> Most e500 are not e500mc (indeed, e500mc is mostly like classic PowerPC at
> the userspace level, not like e500).
The effect of the new test is to generate .PPC.EMB.apuinfo when
gas is given any of -me500, -me500x2 or -me500mc options. Is that
not correct? I freely admit to not being 100% certain.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2009-03-03 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 21:03 Jan Kratochvil
2009-03-02 21:24 ` Daniel Jacobowitz
2009-03-02 21:34 ` Jan Kratochvil
2009-03-03 20:24 ` Thiago Jung Bauermann
2009-03-03 20:31 ` Daniel Jacobowitz
2009-03-03 20:54 ` Peter Bergner
2009-03-03 23:16 ` Alan Modra
2009-03-03 23:30 ` Joseph S. Myers
2009-03-03 23:36 ` Daniel Jacobowitz
2009-03-03 23:48 ` Alan Modra [this message]
2009-03-03 23:54 ` Joseph S. Myers
2009-03-03 23:49 ` Thiago Jung Bauermann
2009-03-03 23:54 ` Alan Modra
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=20090303234833.GE9491@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=bauerman@br.ibm.com \
--cc=bergner@vnet.ibm.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=joseph@codesourcery.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