Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Peter Bergner <bergner@vnet.ibm.com>
Cc: Daniel Jacobowitz <drow@false.org>,
		Thiago Jung Bauermann <bauerman@br.ibm.com>,
		Jan Kratochvil <jan.kratochvil@redhat.com>,
		gdb-patches@sourceware.org
Subject: Re: [patch] Fix power7 ppc64 binaries loading
Date: Tue, 03 Mar 2009 23:16:00 -0000	[thread overview]
Message-ID: <20090303231626.GB9491@bubble.grove.modra.org> (raw)
In-Reply-To: <1236113699.6800.61.camel@otta>

On Tue, Mar 03, 2009 at 02:54:59PM -0600, Peter Bergner wrote:
> 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.

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.

Index: gas/config/tc-ppc.c
===================================================================
RCS file: /cvs/src/src/gas/config/tc-ppc.c,v
retrieving revision 1.147
diff -u -p -r1.147 tc-ppc.c
--- gas/config/tc-ppc.c	26 Feb 2009 22:07:32 -0000	1.147
+++ gas/config/tc-ppc.c	3 Mar 2009 22:54:35 -0000
@@ -2965,10 +3038,7 @@ md_assemble (char *str)
 
 #ifdef OBJ_ELF
   /* Do we need/want a APUinfo section? */
-  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)
     {
       /* These are all version "1".  */
       if (opcode->flags & PPC_OPCODE_SPE)


-- 
Alan Modra
Australia Development Lab, IBM


  reply	other threads:[~2009-03-03 23:16 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 [this message]
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=20090303231626.GB9491@bubble.grove.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=bauerman@br.ibm.com \
    --cc=bergner@vnet.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