From: Doug Evans <dje@transmeta.com>
To: Alan Lehotsky <apl@alum.mit.edu>
Cc: cgen@sources.redhat.com
Subject: contemplating CGEN for VLIW architecture
Date: Wed, 20 Feb 2002 09:18:00 -0000 [thread overview]
Message-ID: <15475.55886.238854.822286@casey.transmeta.com> (raw)
In-Reply-To: <p04330100b89964fb3501@[192.168.1.254]>
Alan Lehotsky writes:
> I guess I'm also wondering if I can build an assembler that looks more like an expression language,
> viz something like
>
>
> REGA = REGB + REGC, if R7 > R8 jump FAIL, REGZ=0x100;
>
> where commas separate the various micro-ops, and the expressions are from the minimal set of + - ^ | &
> separated by white space, etc.
>
> Or is gas ONLY going to work with a traditional
>
> OPCODE OPERANDS,....
>
> style?
Maybe write a separate language that converts one to the other?
Support "if R7 > R8 jump FAIL" on top,
and pass the result to gas which recognizes the "opcode operands,..." style.
prev parent reply other threads:[~2002-02-20 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 6:54 Alan Lehotsky
2002-02-20 6:59 ` matthew green
2002-02-20 8:01 ` John Healy
2002-02-20 7:59 ` Frank Ch. Eigler
2002-02-20 9: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=15475.55886.238854.822286@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=apl@alum.mit.edu \
--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).