|Microcode - generators , compilers email@example.com (kiksik) (2001-06-07)|
|Re: Microcode - generators , compilers Scott.Daniels@Acm.Org (Scott David Daniels) (2001-06-14)|
|Re: Microcode - generators , compilers firstname.lastname@example.org (Preston Gurd) (2001-06-28)|
|From:||"Scott David Daniels" <Scott.Daniels@Acm.Org>|
|Date:||14 Jun 2001 00:27:34 -0400|
|Organization:||Posted via Supernews, http://www.supernews.com|
|Posted-Date:||14 Jun 2001 00:27:34 EDT|
I don't have any good pointers, but perhaps can inspire someone who
does (I tried Google and ACM Digital Library unsuccessfully). The
Foonly corp. (RIP) used a microcode assembler/compiler named "SLOE"
that did code placement on address patterns, and allowed you to
associate names with particular bit patterns that included on, off,
and don't-care. microcode could be put together as long as there were
no conflicts over bits. This latter allowed you to define constraints
by inventing some bits that did nothing more than conflict when
incompatible things were done in the whole operation. Those extra
conflict-resolving bits were called "ghost bits". I would bet the
thing came out of the Stanford AI Lab (or at least from discussions
that originated there), since the two original founders of Foonly came
from there. If you can find SLOE from either Stanford, MIT, or CMU
(or even some references to "ghost bits" that look at all about VLIW),
you may be wandering on to the right track.
-Scott David Daniels
"kiksik" <email@example.com> wrote in message
> I'm new reader now, so please be patient for my low expirience level .
> I'm working on disign of the simple microprocessor. I've designed a
> simple 8 bit architecture.
> I need now any microcode generation or compilation utility(I don't
> know), becouse I have to write the control bits for the execution unit.
> It needs about 50 control bits per microinstruction to serve this unit.
> It is very hard to do it manually for every cycle and instruction
> execution procedure. If anyone can help me please...
Return to the
Search the comp.compilers archives again.