From: Geoff Keating <geoffk@geoffk.org>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: cgen@sources.redhat.com
Subject: Re: field-start and varying word sizes
Date: Tue, 03 Jul 2001 15:12:00 -0000 [thread overview]
Message-ID: <jm1ynxlkcz.fsf@geoffk.org> (raw)
In-Reply-To: <o5wv5pzoy1.fsf.cygnus.local.cgen@toenail.toronto.redhat.com>
fche@redhat.com (Frank Ch. Eigler) writes:
> geoffk wrote:
>
> : [...]
> : I can see why someone might try to write this, but it can't work. It
> : needs to know, as well as lsb0?, the endianess of the CPU.
> : [...]
> : In this case, the right thing to do is to just return
> : (bitrange-start bitrange)
> : [...]
> : 2001-07-03 Geoffrey Keating <geoffk@redhat.com>
> :
> : * ifield.scm (<ifield> 'field-start): Don't look at word-len.
> : [...]
>
>
> Unfortunately this whole area of cgen (and the opcodes/ run-time) is
> so messy that even an obvious looking change is untrustworthy. One
> has to test a whole slew of different targets for confidence -- have
> you done that?
No, only the target I'm working on.
Which targets would you suggest? I'm quite happy to configure & build
a bunch of targets with and without the patch.
--
- Geoffrey Keating <geoffk@geoffk.org>
next prev parent reply other threads:[~2001-07-03 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200107032054.NAA01495.cygnus.local.cgen@geoffk.org>
2001-07-03 14:24 ` Frank Ch. Eigler
[not found] ` <o5wv5pzoy1.fsf.cygnus.local.cgen@toenail.toronto.redhat.com>
2001-07-03 15:12 ` Geoff Keating [this message]
2001-07-03 13:39 Geoff Keating
2001-07-03 14:42 ` Doug Evans
[not found] ` <15170.15391.989073.581389.cygnus.local.cgen@casey.transmeta.com>
2001-07-03 15:32 ` Geoff Keating
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=jm1ynxlkcz.fsf@geoffk.org \
--to=geoffk@geoffk.org \
--cc=cgen@sources.redhat.com \
--cc=fche@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).