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>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] 32/64 mistake in mips_find_saved_regs
Date: Tue, 06 Aug 2002 16:23:00 -0000	[thread overview]
Message-ID: <3D5055FB.674B2E70@redhat.com> (raw)
In-Reply-To: <3D5030EA.9060102@ges.redhat.com>

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.

> As for the below, yes ok.  Can you please also update the comment to
> read something like:
> 
> ``[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.''
> 
> I think that is more correct.

Will do.

> 
> Andrew
> 
> > Here is a test that should check for stack/register size, not
> > whether target == mips64.
> >
> > Fixes four failures in callfuncs.exp, no other regressions.
> >
> >
> >
> > 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.  N32 is not
> >       MIPS64, but it does save 64 bits worth of register.
> >
> > Index: mips-tdep.c
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/mips-tdep.c,v
> > retrieving revision 1.88
> > diff -p -r1.88 mips-tdep.c
> > *** mips-tdep.c       1 Aug 2002 23:10:34 -0000       1.88
> > --- mips-tdep.c       6 Aug 2002 04:32:33 -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,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 saved_reg_size == 4. */
> > !   if (MIPS_SAVED_REGSIZE == 4)
> >       reg_position += MIPS_SAVED_REGSIZE;
> >
> >     /* Fill in the offsets for the float registers which float_mask says


  reply	other threads:[~2002-08-06 23:23 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 [this message]
2002-08-06 17:27     ` Michael Snyder
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=3D5055FB.674B2E70@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