From: "Frank Ch. Eigler" <fche@redhat.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: cgen@sources.redhat.com
Subject: Re: [RFA:] Fix for lsb0? in -gen-extract-word, take 2.
Date: Mon, 24 Jun 2002 20:48:00 -0000 [thread overview]
Message-ID: <20020624234746.A1432@redhat.com> (raw)
In-Reply-To: <Pine.BSF.4.30.0206242149010.46015-100000@dair.pair.com>; from hp@bitrange.com on Mon, Jun 24, 2002 at 09:50:00PM -0400
Hi -
On Mon, Jun 24, 2002 at 09:50:00PM -0400, Hans-Peter Nilsson wrote:
> Here's a less intrusive fix since I couldn't wrap my head around
> what adjustment there should be for the "<<" expression. I
> can't figure out whether it actually has lsb0?-issues at all, so
> I'll not touch it. Again, only tested on the CRIS (wip) target.
> [...]
Let me voice one note of caution regarding this area. cgen is
not fully developed with respect to variable-length instruction
sets, and some other odd cgen-isa parametrizations. This has
been making it necessary to use lsb0=#f for several cpu ports.
I'm worried that modification of something as low-level as
gen-extract-* can easily break these unusual ports.
Unfortunately, only "medium-weird" ports are on the sourceware
cgen repository, so it's possible that a change will break only
a port you don't (yet) have access to.
Anyway, please keep in mind that you're treading on fragile
territory.
- FChE
next prev parent reply other threads:[~2002-06-25 3:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 18:50 Hans-Peter Nilsson
2002-06-24 20:48 ` Frank Ch. Eigler [this message]
2002-06-24 21:06 ` Doug Evans
2002-06-25 3:20 ` Frank Ch. Eigler
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=20020624234746.A1432@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=hp@bitrange.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).