public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: John Healy <jhealy@redhat.com>
To: matthew green <mrg@redhat.com>
Cc: Alan Lehotsky <apl@alum.mit.edu>, cgen@sources.redhat.com
Subject: Re: contemplating CGEN for VLIW architecture
Date: Wed, 20 Feb 2002 08:01:00 -0000	[thread overview]
Message-ID: <3C73C8F2.B0DB7E4@redhat.com> (raw)
In-Reply-To: <9857.1014217112@redhat.com>

As far as I know, the issue is not that cgen can't handle instructions longer than 32 bits, but that all
decodable bits must be within the top 32 bits.   If I understand what is written below correctly, each
element in the VLIW bundle will be 25 bits long so in that respect, I think you'll be ok.

John



matthew green wrote:

>    I'm evaluating a possible port to a VLIW microsequencer (256 bit microword, 25 fields
>    per micro-instruction).
>
>    I guess the good news is that there's ONLY one instruction format :-)
>
>    Any experience out there with such a wide instruction?  I remember seeing some patches a while back
>    to deal with instruction formats >> 32 bits.
>
> cgen supports > 32 bits.  dunno how _much_ further but i think it should
> work today...
>
>
>    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?
>
> last i looked, the guts of the generated gas really seemed to assume
> the latter unfortunately.
>
> .mrg.

  reply	other threads:[~2002-02-20 16:01 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 [this message]
2002-02-20  7:59 ` Frank Ch. Eigler
2002-02-20  9: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=3C73C8F2.B0DB7E4@redhat.com \
    --to=jhealy@redhat.com \
    --cc=apl@alum.mit.edu \
    --cc=cgen@sources.redhat.com \
    --cc=mrg@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).