Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] 32/64 mistake in mips_find_saved_regs
Date: Tue, 06 Aug 2002 17:27:00 -0000	[thread overview]
Message-ID: <3D506515.A75820B9@redhat.com> (raw)
In-Reply-To: <3D5055FB.674B2E70@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

Michael Snyder wrote:
> 
> Andrew Cagney wrote:
> >
> > I believe n32 should be setting mips64 to 1.  Can you please change that. .
> 
> Really?  So you think mips64 specifies 64-bit registers, rather than
> 64 bit addresses?  I'll try the change, and see what happens.

Well, this caused no regressions, so I'll commit it along with the rest.

> > As for the below, yes ok.  Can you please also update the comment to
> > read something like:

Committed in modified form, as follows:

[-- Attachment #2: patch2a.diff --]
[-- Type: text/plain, Size: 2537 bytes --]

2002-08-05  Michael Snyder  <msnyder@redhat.com>

	*  mips-tdep.c (mips_find_saved_regs): Adjust stack according
	to MIPS_SAVED_REGSIZE, not GDB_TARGET_IS_MIPS64.  Enhance comment.
	(mips_gdbarch_init): Set N32 target to be mips64.

Index: mips-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mips-tdep.c,v
retrieving revision 1.89
diff -p -r1.89 mips-tdep.c
*** mips-tdep.c	6 Aug 2002 19:03:40 -0000	1.89
--- mips-tdep.c	7 Aug 2002 00:26:15 -0000
*************** mips_find_saved_regs (struct frame_info 
*** 1371,1379 ****
       were saved.  */
    reg_position = fci->frame + PROC_FREG_OFFSET (proc_desc);
  
!   /* The freg_offset points to where the first *double* register
!      is saved.  So skip to the high-order word. */
!   if (!GDB_TARGET_IS_MIPS64)
      reg_position += MIPS_SAVED_REGSIZE;
  
    /* Fill in the offsets for the float registers which float_mask says
--- 1371,1390 ----
       were saved.  */
    reg_position = fci->frame + PROC_FREG_OFFSET (proc_desc);
  
!   /* Apparently, the freg_offset gives the offset to the first 64 bit
!      saved.
! 
!      When the ABI specifies 64 bit saved registers, the FREG_OFFSET
!      designates the first saved 64 bit register.
! 
!      When the ABI specifies 32 bit saved registers, the ``64 bit saved
!      DOUBLE'' consists of two adjacent 32 bit registers, Hence
!      FREG_OFFSET, designates the address of the lower register of the
!      register pair.  Adjust the offset so that it designates the upper
!      register of the pair -- i.e., the address of the first saved 32
!      bit register.  */
! 
!   if (MIPS_SAVED_REGSIZE == 4)
      reg_position += MIPS_SAVED_REGSIZE;
  
    /* Fill in the offsets for the float registers which float_mask says
*************** mips_gdbarch_init (struct gdbarch_info i
*** 4525,4531 ****
        tdep->mips_last_arg_regnum = A0_REGNUM + 8 - 1;
        tdep->mips_last_fp_arg_regnum = FPA0_REGNUM + 8 - 1;
        tdep->mips_regs_have_home_p = 0;
!       tdep->gdb_target_is_mips64 = 0;
        tdep->default_mask_address_p = 0;
        set_gdbarch_long_bit (gdbarch, 32);
        set_gdbarch_ptr_bit (gdbarch, 32);
--- 4536,4542 ----
        tdep->mips_last_arg_regnum = A0_REGNUM + 8 - 1;
        tdep->mips_last_fp_arg_regnum = FPA0_REGNUM + 8 - 1;
        tdep->mips_regs_have_home_p = 0;
!       tdep->gdb_target_is_mips64 = 1;
        tdep->default_mask_address_p = 0;
        set_gdbarch_long_bit (gdbarch, 32);
        set_gdbarch_ptr_bit (gdbarch, 32);

  reply	other threads:[~2002-08-07  0:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 22:06 Michael Snyder
2002-08-06 13:26 ` Andrew Cagney
2002-08-06 16:23   ` Michael Snyder
2002-08-06 17:27     ` Michael Snyder [this message]
2002-08-07  8:32       ` Andrew Cagney

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=3D506515.A75820B9@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@ges.redhat.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