From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Use -mabi=altivec for AltiVec tests
Date: Sun, 21 Oct 2007 19:37:00 -0000 [thread overview]
Message-ID: <200710211807.l9LI7vCL011126@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20071021130504.GA10828@caradoc.them.org> from "Daniel Jacobowitz" at Oct 21, 2007 09:05:04 AM
Daniel Jacobowitz wrote:
> I don't think this is a good idea. -mabi=altivec is an ABI-changing
> option; you're supposed to match the ABI of your system libraries.
> It will work out OK in practice though since the stack alignment is
> already large enough on powerpc-linux.
Sorry, I didn't consider this controversial, or I would have posted an RFC
first ... I understand it to be general practice to use -mabi=altivec
with applications on Linux, and that should be OK as long as no system
library interface using vector arguments is used. Is this a problem
in other environments?
However, if you prefer, I certainly have no objections to reverting the
patch (or maybe restricting it to Linux only) ...
> I committed a GCC HEAD patch several weeks ago to mark the vector ABI of
> PowerPC object files. I also posted a linker patch to propogate this
> into linked objects and I have the matching patch to GDB to
> auto-detect the correct ABI and support both in GDB. That also
> fixes this test.
Supporting both ABIs in GDB is certainly a good thing. However, the
point of this test case is to verify that GDB implements the AltiVec
ABI correctly, so IMO we really want to exercise that code path, not
bypass it. In fact, if we support both ABIs in GDB, we probably want
to run the test twice, once compiled with -mabi=altivec and once with
-mabi=no-altivec ...
> Unfortunately the linker patch is hung up right now because it notices
> this same dubious action (linking -mabi=altivec and -mabi=no-altivec
> code) and warns about it. That causes a bunch of GCC testcase
> failures. The GCC testcases in question use, but do not actually
> need, -mabi=altivec; they just need a nasty bug in -maltivec
> -mabi=no-altivec fixed and my patch for that didn't get any comments
> :-(
Can you point me to the patch in question? Maybe I can ping David ...
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-21 18:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 13:05 Ulrich Weigand
2007-10-21 18:08 ` Daniel Jacobowitz
2007-10-21 19:37 ` Ulrich Weigand [this message]
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
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=200710211807.l9LI7vCL011126@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