At 08:42 PM 7/5/01 +0100, you wrote:
>Hello all,
>
>No this is not the next proposal for a C-compiler.
>I was just wondering how the compiler is made.
>
>teh company i work for has a processor of which they
>cannot make a c compiler just because it has no
>Orthogonal Instruction Set.
>
>This does not mean anything to me !!

It's basically a steaming pile of B.S. (gee, hope nobody
reads this while they are eating), if that's the only reason.

>Please can some one elaborate ???

"Orthogonal" in this context refers to the instruction
set being "nice" in that, for example, all addressing
modes are supported for all kinds of operands. It
may be slightly more difficult to make a compiler for
a processor that has a non-orthogonal instruction set,
but it does not make it impossible. A compiler does
not have to use every instruction, only enough
instructions to do whatever it is that it has to do.

If you are interested in compiler design, you can
do worse than go to the library and pick up the
old classic, the "dragon book", Compilers, Principles
Techniques and Tools (Aho, Sethi, Ullman). As Walter
Banks said, the basics are quick and easy. The details-
the libraries, error detection and recovery are not
so easy. The PIC instruction set, taking all devices
into account, is a dog's breakfast, IMHO. The existing
vendors are doing quite well, I think.

Best regards,
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Spehro Pefhany --"it's the network..."            "The Journey is the reward"
speff@interlog.com             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com
Contributions invited->The AVR-gcc FAQ is at: http://www.bluecollarlinux.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu