Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: gdb-patches@sources.redhat.com, cagney <cagney@redhat.com>
Subject: [RFA] mips-o64-extract-return-value
Date: Thu, 20 Nov 2003 01:08:00 -0000	[thread overview]
Message-ID: <3FBC13EC.1040202@redhat.com> (raw)

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

Hi Andrew,

This change fixes 100s of FAILs for mips64-elf, 'cause gdb can't
find the function's return value.  It follows some work that you
were apparently doing w.r.t. the mips internal register representation.

I suspect that the same thing needs to be done for mips_eabi_extract...,
but I haven't tested that.  What do you think?

I'll probably try doing something similar for store_return_value too.

Michael


[-- Attachment #2: extract --]
[-- Type: text/plain, Size: 1165 bytes --]

2003-11-19  Michael Snyder  <msnyder@redhat.com>

	* mips-tdep.c (mips_o64_extract_return_value):
	Correct for raw reg / virtual reg scheme.

Index: mips-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mips-tdep.c,v
retrieving revision 1.254
diff -p -r1.254 mips-tdep.c
*** mips-tdep.c	16 Nov 2003 22:46:49 -0000	1.254
--- mips-tdep.c	20 Nov 2003 01:00:31 -0000
*************** mips_o64_extract_return_value (struct ty
*** 4681,4692 ****
    return_value_location (valtype, &hi, &lo);
  
    memcpy (valbuf + lo.buf_offset,
! 	  regbuf + DEPRECATED_REGISTER_BYTE (lo.reg) + lo.reg_offset,
  	  lo.len);
  
    if (hi.len > 0)
      memcpy (valbuf + hi.buf_offset,
! 	    regbuf + DEPRECATED_REGISTER_BYTE (hi.reg) + hi.reg_offset,
  	    hi.len);
  }
  
--- 4681,4692 ----
    return_value_location (valtype, &hi, &lo);
  
    memcpy (valbuf + lo.buf_offset,
! 	  regbuf + DEPRECATED_REGISTER_BYTE (NUM_REGS + lo.reg) + lo.reg_offset,
  	  lo.len);
  
    if (hi.len > 0)
      memcpy (valbuf + hi.buf_offset,
! 	    regbuf + DEPRECATED_REGISTER_BYTE (NUM_REGS + hi.reg) + hi.reg_offset,
  	    hi.len);
  }
  

             reply	other threads:[~2003-11-20  1:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  1:08 Michael Snyder [this message]
2003-11-20  1:23 ` Andrew Cagney
2003-11-20 21:28   ` Michael Snyder
2003-11-20 21:54     ` Andrew Cagney
2003-11-21  1:04       ` Michael Snyder
2003-11-21 16:14         ` Andrew Cagney
2003-11-21 21:53           ` Michael Snyder
2003-11-22  0:13             ` Andrew Cagney
2003-11-22  1:01               ` Michael Snyder
2003-11-22  1:05                 ` Daniel Jacobowitz
2003-11-25 22:04                   ` Michael Snyder
2003-11-25 22:15   ` Michael Snyder

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=3FBC13EC.1040202@redhat.com \
    --to=msnyder@redhat.com \
    --cc=cagney@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