From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] PowerPC ABI detection and overrides
Date: Mon, 29 Oct 2007 18:38:00 -0000 [thread overview]
Message-ID: <20071029183229.GA10700@caradoc.them.org> (raw)
In-Reply-To: <200710291811.l9TIBRpc017629@d12av02.megacenter.de.ibm.com>
On Mon, Oct 29, 2007 at 07:11:27PM +0100, Ulrich Weigand wrote:
> > You will need
> > a relatively current GCC and very current linker for the auto tests
> > to all pass.
>
> Any chance of making those tests XFAIL instead of FAIL if the
> toolchain is too old?
Most will pass anyway. The default ABI selection is going to be
AltiVec because the default set of registers include AltiVec
registers. I'll try to find some tools I can use to confirm that
before I check it in though.
I can probably come up with an XFAIL approach. I'll need some other
way to check that the attributes are present. Maybe objdump.
> However, this may not be quite as bad as it seems: note that while
> in your bugzilla report, you're refering to use of "__vector int",
> this actually doesn't work: the "AltiVec vector" types introduced
> via the __vector or vector keywords are only available in the first
> place if you use -maltivec; otherwise that code is rejected with a
> syntax error anyway.
Thanks, I'd forgotten about that.
> So I would suggest that GDB interprets the "generic" case always
> as the "-maltivec -mabi=no-altivec" situation, and expects 16-byte
> vector return values in general-purpose registers. This would also
> fix our test cases (as those use the Altivec vector syntax and thus
> reqiure -maltivec anyway).
Interesting. Very interesting. I'll double-check that this works
and switch to it if it does. Then maybe I can test more of the cases.
> Hmmm, I would have hoped we could get away from directly refering
> to the BFD in the gdbarch_init routine ... It would be nicer to
> more strictly distinguish between detecting ABI properties from
> the BFD (in the *sniffer*), and installing an gdbarch handler
> supporting a particular set of ABI properties (in the gdbarch_init
> routine).
>
> This would allow to request a specific gdbarch in the situation
> where you know exactly which ABI properties you need, but don't
> have any BFD handy ...
Can you give me an example of when you want to do that? In general
I've been moving away from it - there's too much extra bookkeeping
that the BFD does for us.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-29 18:32 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 [this message]
2007-10-29 19:02 ` Ulrich Weigand
2007-10-29 19:16 ` Daniel Jacobowitz
2007-10-29 19:27 ` Ulrich Weigand
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=20071029183229.GA10700@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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