public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Michael Meissner <cgen-mail@the-meissners.org>
Cc: cgen@sources.redhat.com
Subject: What is the state of cgen for architectures like the IA-64?
Date: Fri, 16 May 2003 20:18:00 -0000	[thread overview]
Message-ID: <16069.18271.734282.633473@casey.transmeta.com> (raw)
In-Reply-To: <20030515013013.GA1220@tiktok.the-meissners.org>

Michael Meissner writes:
 > I tried building the ia64 opcodes, and it looks like it has bit-rotted

I believe what's there now is a work-in-progress / experiment.

 > So is cgen currently up to handling such an architecture without significant
 > hacking?

Dunno.  I think it'll require some work.
I suspect it's not significant surgery but then again I'll bet it's
far more than a Blue's Clues bandaid.
(parental humor there for those without kids :-)

 > If the IA-64 is not fleshed out, is there another target in the
 > public sources that would be more appropriate to look at?

You might try the m32r port, though its kind of instruction
packing is far simpler.

I have started something in the description language to use to
describe such architectures.  grep for frame in m32r.cpu.
It's not currently used by the m32r port though and the real work
is in using the data (it's not rocket science though).
It came after and I haven't had time to finish it.

 > faster for me to do the port
 > the old fashioned way.

That may well be true.  In the end I believe it'd be less fun though. :-)

And with a cgen description of the port, you open yourself up to
other kinds of things one might want to do.

      parent reply	other threads:[~2003-05-16 20:18 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
2003-05-16 20:18 ` Doug Evans [this message]

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=16069.18271.734282.633473@casey.transmeta.com \
    --to=dje@transmeta.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).