From: Peter Bergner <bergner@vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org,
Alan Modra <amodra@bigpond.net.au>
Subject: Re: [patch] Fix power7 ppc64 binaries loading
Date: Tue, 03 Mar 2009 20:54:00 -0000 [thread overview]
Message-ID: <1236113699.6800.61.camel@otta> (raw)
In-Reply-To: <20090303203050.GA2551@caradoc.them.org>
On Tue, 2009-03-03 at 15:30 -0500, Daniel Jacobowitz wrote:
> On Tue, Mar 03, 2009 at 05:24:41PM -0300, Thiago Jung Bauermann wrote:
> > Does apuinfo get generated for every binary in every platform? Why
> > wasn't this an issue before? It just started being generated recently?
>
> I assume it is only generated for specific ISA extensions - and that
> both POWER7 and e500 have them. GAS says:
>
> if (ppc_cpu & (PPC_OPCODE_SPE
> | PPC_OPCODE_ISEL | PPC_OPCODE_EFS
> | PPC_OPCODE_BRLOCK | PPC_OPCODE_PMR | PPC_OPCODE_CACHELCK
> | PPC_OPCODE_RFMCI))
With Power ISA 2.06 which was just recently announced on power.org, the
isel instruction has now moved from an optional instruction to a required
instruction. The POWER7 processor is ISA 2.06 compliant, so it has the
PPC_OPCODE_ISEL flag set which triggers this...as will all future Power
processors.
That said, I have no idea what the apuinfo section is being used for.
Peter
next prev parent reply other threads:[~2009-03-03 20:54 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 [this message]
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
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=1236113699.6800.61.camel@otta \
--to=bergner@vnet.ibm.com \
--cc=amodra@bigpond.net.au \
--cc=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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