Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Use -mabi=altivec for AltiVec tests
Date: Wed, 24 Oct 2007 20:47:00 -0000	[thread overview]
Message-ID: <20071024204239.GO10943@caradoc.them.org> (raw)
In-Reply-To: <200710211807.l9LI7vCL011126@d12av02.megacenter.de.ibm.com>

On Sun, Oct 21, 2007 at 08:07:57PM +0200, Ulrich Weigand wrote:
> 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) ...

My understanding (courtesy of Geoff Keating) is that on most PowerPC
targets this only affects the passing of vector registers.  On some
(powerpc-eabi; I am not sure if there are others, but I do not know
of any) it increases the required stack alignment.  If your CRT files
don't do this, then saving the vector registers may do bad things
to your stack frame.

I know my local GDB works both with -mabi=altivec and without it,
because I run this test in two multilibs :-)

For now, what do you think we should do about the option?  Restrict it
to Linux?

> > 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 ...

http://gcc.gnu.org/ml/gcc-patches/2007-08/msg00438.html

Perhaps I should ping that now that the .gnu_attribute bit went in
separately.  Actually, no, the patch predated my improved
understanding of the stack alignment magic.  It might be right
for powerpc-eabi, but powerpc-linux actually does have a sufficiently
aligned stack so it ought to save them properly.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-10-24 20:42 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
2007-10-24 20:47     ` Daniel Jacobowitz [this message]
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=20071024204239.GO10943@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