Richard,
Thanks a lot for the detailed explanation. I need some time to digest,
since this is my first experience doing a gcc backend port.
> Probably most of that was just telling you what you already knew, sorry.
Not really, I am new to most of these concepts. At this stage, this is
exactly th
Omar <[EMAIL PROTECTED]> writes:
> 1-The c816's port is heavily using the c816.c instead of better
> describing the cpu in the c816.md file. For instance, looking at the
> define_insn movhi:
> ;; movhi
> (define_insn "movhi"
> [(set (match_operand:HI 0 "general_operand" "=g")
>(match_oper
Hi All,
BACKGROUND:
Downloaded the source code of the Xemics CoolRISC gcc port from Raisonance's
website (ftp://www.raisonance.com/pub/CoolRISC/cool3_2.zip). I
concluded that the port is based in gcc 3.2 from looking at the NEWS
file in the gcc folder.
I what to bring to this gcc port up to the l
