From: Johan Rydberg <johan.rydberg@netinsight.se>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: 64-bit port using CGEN
Date: Wed, 16 May 2001 08:05:00 -0000 [thread overview]
Message-ID: <3B029755.6AFE5C1D@netinsight.se> (raw)
In-Reply-To: <o51yppe4at.fsf@toenail.toronto.redhat.com>
"Frank Ch. Eigler" wrote:
>
> johan.rydberg wrote:
>
> : [...]
> : First of all, opcode values are truncated to zero:
> :
> : static const CGEN_IFMT ifmt_j = {
> : 64, 64, 0xe000000000000000, { { F (F_OPC) }, { F (F_ABS61) }, { 0 } }
> : };
> : pxs-opc.c:55: warning: large integer implicitly truncated to unsigned type
>
> Yup, known problem. I suspect a good solution is to define
> CGEN_INSN_INT to be "long long" for such extra-wide targets. (That
> will in turn require that pervasive assumptions that CGEN_INSN_INT is
> 32 bits wide be corrected.)
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.
> : [...]
> : Second,
> : The genereated insert and extract code aborts when word length is larger than
> : 32 bit. From /opcodes/cgen-ibld.in: [...]
>
> 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.
next prev parent reply other threads:[~2001-05-16 8:05 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 [this message]
2001-05-16 8:09 ` Frank Ch. Eigler
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=3B029755.6AFE5C1D@netinsight.se \
--to=johan.rydberg@netinsight.se \
--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).