From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>,
gdb-patches@sourceware.org,
Peter Bergner <bergner@vnet.ibm.com>
Subject: Re: [patch] Fix power7 ppc64 binaries loading
Date: Tue, 03 Mar 2009 20:24:00 -0000 [thread overview]
Message-ID: <1236111881.30573.61.camel@localhost.localdomain> (raw)
In-Reply-To: <20090302213340.GA7433@host0.dyn.jankratochvil.net>
El lun, 02-03-2009 a las 22:33 +0100, Jan Kratochvil escribió:
> On Mon, 02 Mar 2009 22:24:03 +0100, Daniel Jacobowitz wrote:
> > Did you test this on an e500 binary? "any" won't work, we should
> > probably parse the apuinfo dump instead of assuming it always means
> > e500. SPE is incompatible with classic FP.
>
> No e500 test by hand. But GDB does not work out of the box even for power7
> (and possibly others).
>
> I agree it may be a regression for e500 binaries. Although the second patch
> makes it possible to handle all using `set powerpc disassembler-options'.
> I agree apuinfo should be parsed.
Does apuinfo get generated for every binary in every platform? Why
wasn't this an issue before? It just started being generated recently?
In any case, if it tells which processor model the binary needs, then it
could be used as method for an "auto" setting in disassembler-options.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-03-03 20:24 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 [this message]
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
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=1236111881.30573.61.camel@localhost.localdomain \
--to=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