Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Luis Machado <luisgpm@linux.vnet.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH-ppc 0/5] Add feature description for new VSX register    set
Date: Fri, 25 Jul 2008 21:46:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0807252138300.10499@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1217021353.5922.121.camel@localhost.localdomain>

On Fri, 25 Jul 2008, Thiago Jung Bauermann wrote:

> On Fri, 2008-07-25 at 21:01 +0000, Joseph S. Myers wrote:
> > On Fri, 25 Jul 2008, Luis Machado wrote:
> > > This is a patch series to enable POWER7 VSX register set support in GDB.
> > > The VSX registers' layout is as follows:
> > 
> > Will IBM be making appropriate proposals regarding these registers in the 
> > Power.org ABI working group?  The obvious things that need defining 
> > include DWARF debug/unwind information handling of the registers, and 
> > what's call-saved / call-clobbered, plus ABI handling of any new 
> > C-language datatypes.
> 
> Regarding call-saved / call-clobbered there's no option really. VSX
> registers follow the saved-ness of the registers they overlap with
> (either floating point or altivec).

So will some of the bits that don't overlap be call-saved?  If so, they 
need setjmp/longjmp support and unwind support, including in the signal 
unwind code in GCC.  I presume such patches to the other toolchain 
components will follow in due course if needed.

-- 
Joseph S. Myers
joseph@codesourcery.com


  reply	other threads:[~2008-07-25 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 20:16 Luis Machado
2008-07-25 21:01 ` Joseph S. Myers
2008-07-25 21:30   ` Thiago Jung Bauermann
2008-07-25 21:46     ` Joseph S. Myers [this message]
2008-07-26  3:50       ` Luis Machado
2008-07-26 11:20         ` Joseph S. Myers
2008-08-02  3:27 ` Thiago Jung Bauermann
2008-08-08 15:16   ` Luis Machado
2008-08-14 19:33     ` Ulrich Weigand
2008-08-15 15:49       ` Luis Machado

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=Pine.LNX.4.64.0807252138300.10499@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.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