From: Richard Earnshaw <rearnsha@arm.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] arm_store_return_value, big-endian (take 2)
Date: Thu, 14 Nov 2002 01:50:00 -0000 [thread overview]
Message-ID: <200211140949.gAE9nxm10294@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 13 Nov 2002 11:55:04 PST." <3DD2AE18.C1D0E978@redhat.com>
> Oh, I see. Yes, it's no longer necessary. But if it's not so hard,
> and you already see what's necessary, why not just do it instead of
> ragging on me to do it? ;-)
>
Because I don't have a big-endian world in which I can test it.
> This what you have in mind? Please just take it from here, I really
> didn't intend to spend this much time and energy on it.
Nope, now you've broken larger-than-word objects.
>
> 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 13 Nov 2002 19:48:21 -0000
> *************** arm_store_return_value (struct type *typ
> *** 2417,2424 ****
> break;
> }
> }
> ! else
> ! write_register_bytes (ARM_A1_REGNUM, valbuf, TYPE_LENGTH (type));
> }
>
> /* Store the address of the place in which to copy the structure the
> --- 2417,2424 ----
> break;
> }
> }
> ! else
> ! write_register (ARM_A1_REGNUM, unpack_long (type, valbuf);
> }
>
> /* Store the address of the place in which to copy the structure the
>
prev parent reply other threads:[~2002-11-14 9:50 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
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 [this message]
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=200211140949.gAE9nxm10294@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.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