|
Message
From: Marko Mlinar <markom@o...>
Date: Tue, 16 Jan 2001 17:55:59 +0200
Subject: Re: [openrisc] Custom Unit Compiler
Hi Oliver!
> So the custom unit compiler converts ANSI C to verilog, ok.
> I can kind of see what it is doing, something along the lines
> of taking a data flow graph and scheduling it in parallel hardware?
yes.
> It seems to have the intermediate step of converting it to the or1k ISA?
> And you say you can choose functions to be converted.
Yes first you run profile, to see which functions take most of the time.
> Would it be possible for you to give me an example piece of
> ANSI C code that you converted and a quick set of instructions
> on how to convert it to verilog using or1ksim's cuc?
Basically you can put anything ANSI in it and compile it for or1k.
You must first enable the profiling and run the application, for any number of
cycles. then write 'cuc'. Then 'p' or 'profile' you will see a list of
functions there.
I don't quite remember what is the current status on the CVS (probably very
beta), but I actually menaged to run some RTL simulations (which worked, of
course) with memory accesses and so on.
I am still planning to work on the project, just haven't got any free time
lately (~6 mon ;)).
> Also could you give me some references (books, papers, websites)
> about the techniques you used in the cuc?
I don't know of one. Although I searched very much for this kind of stuff on
the internet nobody so far took this approach of compiling directly into HW
(not creating some state machine, CPU or something like that).
Marko
|
 |
Browse
