From: fche@redhat.com (Frank Ch. Eigler)
To: Michael Meissner <cgen-mail@the-meissners.org>
Cc: cgen@sources.redhat.com
Subject: Re: What is the state of cgen for architectures like the IA-64?
Date: Thu, 15 May 2003 19:05:00 -0000 [thread overview]
Message-ID: <o54r3w2fp9.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <20030515013013.GA1220@tiktok.the-meissners.org>
Hi, Mike -
> I'm doing a port for a new machine that has instruction encoding where
> instructions are logically of the format:
> |A |B |
> The instructions are then packed into a field of the form:
> |C |B1 |B2 |B3 |
> where C is an encoding for A1, A2, and A3. [...]
> So is cgen currently up to handling such an architecture without significant
> hacking? [...]
I don't think you'll find much direct support for this. However,
there are enough C hooks available to insert your own instruction
packing/unpacking routines into the opcodes or simulator. With such
routines around the cgen-generated kernel, the job is reduced to
modelling only the logical format of the instructions in cgen.
- FChE
next prev parent reply other threads:[~2003-05-15 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 1:31 Michael Meissner
2003-05-15 19:05 ` Frank Ch. Eigler [this message]
2003-05-16 20:18 ` Doug Evans
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=o54r3w2fp9.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=cgen-mail@the-meissners.org \
--cc=cgen@sources.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).