Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: gdb-patches@sources.redhat.com, rearnsha@arm.com,
	cagney@redhat.com, kevinb@redhat.com
Subject: [RFA] arm_extract_return_value, big-endian
Date: Wed, 06 Nov 2002 13:30:00 -0000	[thread overview]
Message-ID: <3DC989E0.DCFDC68A@redhat.com> (raw)

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

[This doesn't seem to have gone out.  Excuse me if it appears twice]

One of you arm-savvy guys check me out on this:
it seems logical, and it fixes two fails in callfuncs with -mbig-endian.

Michael

[-- Attachment #2: arm.patch --]
[-- Type: text/plain, Size: 848 bytes --]

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

	* arm-tdep.c (arm_extract_return_value): Handle offset of 
	small types on big-endian machines.

Index: arm-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/arm-tdep.c,v
retrieving revision 1.74
diff -p -r1.74 arm-tdep.c
*** arm-tdep.c	1 Nov 2002 21:21:49 -0000	1.74
--- arm-tdep.c	6 Nov 2002 01:54:36 -0000
*************** arm_extract_return_value (struct type *t
*** 2274,2279 ****
--- 2274,2284 ----
  	  break;
  	}
      }
+   else if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG)
+     memcpy (valbuf, 
+ 	    &regbuf[REGISTER_BYTE (ARM_A1_REGNUM)] 
+ 	     + (REGISTER_RAW_SIZE (ARM_A1_REGNUM) - TYPE_LENGTH (type)), 
+ 	    TYPE_LENGTH (type));
    else
      memcpy (valbuf, &regbuf[REGISTER_BYTE (ARM_A1_REGNUM)],
  	    TYPE_LENGTH (type));

             reply	other threads:[~2002-11-06 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 13:30 Michael Snyder [this message]
2002-12-03  7:33 ` Fernando Nasser
2002-12-03  7:41 ` Fernando Nasser
2002-12-04  2:02   ` Richard Earnshaw
2003-01-07 23:46     ` Michael Snyder
2003-01-08  9:48       ` Richard Earnshaw

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=3DC989E0.DCFDC68A@redhat.com \
    --to=msnyder@redhat.com \
    --cc=cagney@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.com \
    --cc=rearnsha@arm.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