From: "Frank Ch. Eigler" <fche@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com
Subject: Re: bad shifts generated in sim code
Date: Fri, 13 Dec 2002 08:49:00 -0000 [thread overview]
Message-ID: <20021213114902.B26639@redhat.com> (raw)
In-Reply-To: <200212100840.AAA12342@xris-athlon.transmeta.com>; from dje@transmeta.com on Tue, Dec 10, 2002 at 12:40:08AM -0800
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
Hi -
On Tue, Dec 10, 2002 at 12:40:08AM -0800, Doug Evans wrote:
> I found these in sim/m32r/decodex.c
> unsigned int val = (((insn >> -8) & (3 << 0)));
> unsigned int val = (((insn >> -12) & (1 << 0)));
> [...]
Do these bad shifts still occur with current cgen?
FWIW, working on sim/m32r may be a short-lived pleasure, if the
target-obsoleting eagerness of gdb guys ends up getting that target
removed. You're welcome to work in sid land. :-)
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-12-13 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 0:40 Doug Evans
2002-12-10 13:41 ` Ben Elliston
2002-12-13 8:49 ` Frank Ch. Eigler [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=20021213114902.B26639@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).