Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Gilliam <pgilliam@us.ibm.com> (by way of Paul Gilliam <pgilliam@us.ibm.com>)
To: gdb-patches@sources.redhat.com
Subject: [COMMITTED] allow gdb to access altivec registers - OK to commit?
Date: Tue, 01 Nov 2005 21:11:00 -0000	[thread overview]
Message-ID: <200511011313.52576.pgilliam@us.ibm.com> (raw)

On Monday 31 October 2005 13:56, Paul Gilliam wrote:
> I revised the ChangeLog entry to note that this change affects GNU/Linux only.
> 
> OK to commit?  (was the previous posting by Kevin an OK to commit?)
> 
> -=# Paul #=-
> 
> PS:  I realy want this to go int 6.4!
> 
> 2005-10-31  Paul Gilliam  <pgilliam@us.ibm.com>
> 
>         * rs6000-tdep.c (rs6000_gdbarch_init): On GNU/Linux only, assume
> 	 that bfd_mach_ppc64 has altivec unit, just like bfd_mach_ppc.
> 
> Index: rs6000-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/rs6000-tdep.c,v
> retrieving revision 1.246
> diff -a -u -p -r1.246 rs6000-tdep.c
> --- rs6000-tdep.c       14 Oct 2005 20:17:11 -0000      1.246
> +++ rs6000-tdep.c       21 Oct 2005 22:44:15 -0000
> @@ -3376,10 +3376,21 @@ rs6000_gdbarch_init (struct gdbarch_info
> 
>    switch (info.osabi)
>      {
> +    case GDB_OSABI_LINUX:
> +      /* FIXME: pgilliam/2005-10-21: Assume all PowerPC 64-bit linux systems
> +         have altivec registers.  If not, ptrace will fail the first time it's
> +         called to access one and will not be called again.  This wart will
> +         be removed when Daniel Jacobowitz's proposal for autodetecting target
> +         registers is implimented. */
> +      if ((v->arch == bfd_arch_powerpc) && ((v->mach)== bfd_mach_ppc64))
> +        {
> +          tdep->ppc_vr0_regnum = 71;
> +          tdep->ppc_vrsave_regnum = 104;
> +        }
> +      /* Fall Thru */
>      case GDB_OSABI_NETBSD_AOUT:
>      case GDB_OSABI_NETBSD_ELF:
>      case GDB_OSABI_UNKNOWN:
> -    case GDB_OSABI_LINUX:
>        set_gdbarch_unwind_pc (gdbarch, rs6000_unwind_pc);
>        frame_unwind_append_sniffer (gdbarch, rs6000_frame_sniffer);
>        set_gdbarch_unwind_dummy_id (gdbarch, rs6000_unwind_dummy_id);
> 
> 



             reply	other threads:[~2005-11-01 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 21:11 Paul Gilliam [this message]
2005-11-02  0:16 ` Daniel Jacobowitz
2005-11-02  1:03   ` Paul Gilliam
2005-11-02  4:28     ` Paul Gilliam
2005-11-02 14:54     ` Daniel Jacobowitz
2005-11-02 14:52       ` Daniel Jacobowitz

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=200511011313.52576.pgilliam@us.ibm.com \
    --to=pgilliam@us.ibm.com \
    --cc=gdb-patches@sources.redhat.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