From: Kazu Hirata <kazu@cs.umass.edu>
To: msnyder@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Unreviewed patches
Date: Sat, 01 Feb 2003 03:23:00 -0000 [thread overview]
Message-ID: <20030131.222329.93642824.kazu@cs.umass.edu> (raw)
In-Reply-To: <3E3B229D.67F2E805@redhat.com>
Hi Michael,
> Yes, thanks. My problem is this: your patch uses a host-order
> sign-extend to simulate a target-order sign-extend. If the host
> and target have different byte orders, you lose. That's probably
> why the simulator uses breg[] to fetch bytes, instead of using
> wreg and masking.
>
> I suggest that it would be comparatively easy to extend the
> breg[] array so that it would cover at least the first three
> bytes in the register (and possibly all four, just because
> it's no extra effort). Something like the attached.
>
> Then the code that references breg[] does not need to change.
I understand your concern. But then if GET_W_REG may give a
byte-swapped value, would the following be endian unsafe?
case O (O_ADD, SW):
rd = GET_W_REG (code->dst.reg);
ea = fetch (&code->src);
res = rd + ea;
goto alu16;
The addition is done in host-order.
Kazu Hirata
next prev parent reply other threads:[~2003-02-01 3:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 6:03 Kazu Hirata
2003-01-31 2:36 ` Michael Snyder
2003-01-31 4:54 ` Kazu Hirata
2003-02-01 1:27 ` Michael Snyder
2003-02-01 3:23 ` Kazu Hirata [this message]
2003-02-03 20:30 ` Michael Snyder
2003-02-03 23:30 ` Kazu Hirata
2003-02-05 22:41 ` Michael Snyder
-- strict thread matches above, loose matches on Subject: below --
2007-10-11 14:51 Kazu Hirata
2007-10-04 12:04 Kazu Hirata
2003-01-17 4:33 Kazu Hirata
2002-07-01 6:55 Joern Rennecke
2002-07-01 8:47 ` Elena Zannoni
2002-07-01 10:10 ` Joern Rennecke
2002-07-01 14:24 ` Elena Zannoni
2002-07-01 15:01 ` Joern Rennecke
2002-07-02 12:32 ` Elena Zannoni
2002-07-03 13:49 ` Joern Rennecke
2002-07-12 4:59 ` Elena Zannoni
2002-07-12 5:47 ` Joern Rennecke
2002-07-12 8:23 ` Andrew Cagney
2002-07-17 11:30 ` Joern Rennecke
2002-07-17 13:04 ` Andrew Cagney
2002-08-05 6:47 ` Elena Zannoni
2002-07-12 11:36 ` Elena Zannoni
2002-06-19 14:29 Joern Rennecke
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=20030131.222329.93642824.kazu@cs.umass.edu \
--to=kazu@cs.umass.edu \
--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