From: "Frank Ch. Eigler" <fche@redhat.com>
To: Johan Rydberg <johan.rydberg@netinsight.se>
Cc: cgen@sources.redhat.com
Subject: Re: 64-bit port using CGEN
Date: Wed, 16 May 2001 08:09:00 -0000 [thread overview]
Message-ID: <20010516110925.F16050@redhat.com> (raw)
In-Reply-To: <3B029755.6AFE5C1D@netinsight.se>
Hi -
On Wed, May 16, 2001 at 05:05:57PM +0200, Johan Rydberg wrote:
: [..]
: > Yup, known problem. I suspect a good solution is to define
: > CGEN_INSN_INT to be "long long" for such extra-wide targets. [...]
:
: Yes. This is what I have done. I also had to change some of the
: mask generation statements so that it generates a correct mask.
Yes; I would expect collateral changes in other places too.
: > : [...]
: > Our very own Stan Cox has submitted a patch that aims to work around
: > this problem using a different approach than the "long long" idea above:
: >
: > http://sources.redhat.com/ml/cgen/2001-q2/msg00003.html
:
: Ok. I will try this patch and see if to works for my port.
If you go the "long long"=CGEN_INSN_INT route, you may not need this
patch. (It emulates longer words as an array of plain 32-bit ones.)
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7ApgkVZbdDOm/ZT0RAlVMAJ41JDV5clkt+0MmlL+JsemCcof9LgCdGwB2
+uKt28taNmjFCwTUizBTI54=
=Md86
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-05-16 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 17:10 Johan Rydberg
2001-05-15 19:36 ` Eric Christopher
2001-05-15 19:39 ` Johan Rydberg
2001-05-15 19:42 ` Eric Christopher
2001-05-15 19:46 ` Johan Rydberg
2001-05-15 20:15 ` matthew green
2001-05-15 20:24 ` Johan Rydberg
[not found] ` <3B01F306.4152A19C.cygnus.local.cgen@netinsight.se>
2001-05-16 7:50 ` Frank Ch. Eigler
2001-05-16 8:05 ` Johan Rydberg
2001-05-16 8:09 ` Frank Ch. Eigler [this message]
2001-05-16 8:17 ` Johan Rydberg
2001-05-15 20:15 ` matthew green
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=20010516110925.F16050@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=johan.rydberg@netinsight.se \
/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).