From: Richard Earnshaw <rearnsha@arm.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com, cagney@redhat.com,
kevinb@redhat.com, rearnsha@arm.com
Subject: Re: [RFA] arm_store_return_value, big-endian (take 2)
Date: Thu, 07 Nov 2002 10:26:00 -0000 [thread overview]
Message-ID: <200211071825.gA7IPEM32490@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 06 Nov 2002 16:27:29 PST." <3DC9B371.94245DDE@redhat.com>
> This fixes up offsets in arm_store_return_value for big-endian targets,
> just as my first patch did for arm_extract_return_value.
>
> This supercedes the patch by the same name, which seems to have
> been bollixed by an incomprehensible but reproducable bug in
> gnu patch.
>
> 2002-11-06 Michael Snyder <msnyder@redhat.com>
>
> * arm-tdep.c (arm_store_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 7 Nov 2002 00:22:13 -0000
> *************** arm_store_return_value (struct type *typ
> *** 2417,2422 ****
> --- 2417,2425 ----
> break;
> }
> }
> + else if (TYPE_LENGTH (type) < REGISTER_RAW_SIZE (A1_REGNUM))
> + write_register_bytes (REGISTER_RAW_SIZE (A1_REGNUM) - TYPE_LENGTH (type),
> + valbuf, TYPE_LENGTH (type));
> else
> write_register_bytes (ARM_A1_REGNUM, valbuf, TYPE_LENGTH (type));
> }
>
Leaving asside the issue of the correctness of write_register_bytes (note
to self, must finish of my register patches), I don't think this is
correct -- in fact, I think it's also wrong for little-endian as well.
What should happen is that the smaller-than-word value should be
zero/sign-extended to 32 bits and then the whole thing stored in A1_REGNUM.
R.
next prev parent reply other threads:[~2002-11-07 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 16:27 Michael Snyder
2002-11-07 10:26 ` Richard Earnshaw [this message]
2002-11-07 19:19 ` Michael Snyder
2002-11-08 1:57 ` Richard Earnshaw
2002-11-08 11:37 ` Michael Snyder
2002-11-09 3:55 ` Richard Earnshaw
2002-11-11 17:15 ` Michael Snyder
2002-11-12 2:15 ` Richard Earnshaw
2002-11-13 11:55 ` Michael Snyder
2002-11-14 1:50 ` 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=200211071825.gA7IPEM32490@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=cagney@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=msnyder@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