From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] PowerPC ABI detection and overrides
Date: Mon, 29 Oct 2007 19:27:00 -0000 [thread overview]
Message-ID: <200710291924.l9TJOC7h004125@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20071029191328.GA13900@caradoc.them.org> from "Daniel Jacobowitz" at Oct 29, 2007 03:13:28 PM
Daniel Jacobowitz wrote:
> Ignoring abfd is deliberate; we should be able to construct the same
> arch with or without a BFD. But ignoring things derived from abfd is
> a bug indeed. The MIPS target stashes ELF flags in its tdep structure
> for this reason. PowerPC may not need that heavyweight check, but it
> does need some other things, e.g., sysv_abi. Actually that's the only
> one that I see that ought to be checked. Maybe that will fix the bug?
Yes, the bug I had was related to sysv_abi. And in fact, sysv_abi should
be fully detectable simply from looking at info.osabi, it should IMO not
be computed independently from the BFD. That's why I thought the proper
way to fix this problem was to stop looking directly at the BFD ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-10-29 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 13:05 [commit] Use -mabi=altivec for AltiVec tests Ulrich Weigand
2007-10-21 18:08 ` Daniel Jacobowitz
2007-10-21 19:37 ` Ulrich Weigand
2007-10-24 20:47 ` Daniel Jacobowitz
2007-10-29 18:04 ` Ulrich Weigand
2007-10-29 18:06 ` Daniel Jacobowitz
2007-10-29 18:32 ` Ulrich Weigand
2007-10-25 20:32 ` [rfc] PowerPC ABI detection and overrides Daniel Jacobowitz
2007-10-29 18:27 ` Ulrich Weigand
2007-10-29 18:38 ` Daniel Jacobowitz
2007-10-29 19:02 ` Ulrich Weigand
2007-10-29 19:16 ` Daniel Jacobowitz
2007-10-29 19:27 ` Ulrich Weigand [this message]
2007-10-30 20:12 ` Daniel Jacobowitz
2007-10-30 21:12 ` Ulrich Weigand
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=200710291924.l9TJOC7h004125@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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