search for: ttas

...ng system to make calls to. I/O is done by fiddling bits in function units. The plan is to use LLVM as a front end, and write a back end that maps LLVM byte code to the target architecture. One of the main issues is instruction scheduling, in order to utilize the instruction level parallelism that TTAs potentially provide. Much of libc is just convenience functions expressible in plain C, so my plan is to compile newlib to byte code libraries, which would be linked with the application at the byte code level. The linked byte code would then be passed to the back end and mapped to the final targe...

...sor RTL (VHDL and Verilog generation supported) and parallel program binaries. Processor customization points include the register files, function units, supported operations, and the interconnection network. Release Highlights ================== - Support for LLVM 5.0. - Support for little-endian TTAs. - VLIWConnectIC: An explorer plugin which creates a VLIW-like interconnection network and creates a separate RF for each distinct bus width. Download ======== Get the release via git by cloning the release branch: git clone -b release-1.16 https://github.com/cpc/tce.git tce-1.16 Acknowledge...

On Jun 9, 2011, at 8:09 PM, David A. Greene wrote: > Note that things like instruction frequencies are highly ISA- > dependent. If possible, it is best to evaluate your ideas on more > than one target, just to see what the effects are. What other sorts > of things do you want to study? > > If, long-term, you are planning to do serious studies of performance >

...is done by fiddling bits in > function units. > > The plan is to use LLVM as a front end, and write a back > end that maps LLVM byte code to the target architecture. > One of the main issues is instruction scheduling, in order to > utilize the instruction level parallelism that TTAs potentially > provide. > > Much of libc is just convenience functions expressible in plain C, > so my plan is to compile newlib to byte code libraries, which > would be linked with the application at the byte code level. > The linked byte code would then be passed to the back end...

Hi Pertti, On Thu, 2006-11-09 at 15:29 +0200, Pertti Kellomäki wrote: > I managed to compile newlib with llvm-gcc yesterday. That > is, the machine independent part is now basically done, and > the syscall part contains no-op stubs provided by libgloss. > I haven't tested the port yet, but since newlib has already > been ported to many architectures, I would be pretty surprised

I managed to compile newlib with llvm-gcc yesterday. That is, the machine independent part is now basically done, and the syscall part contains no-op stubs provided by libgloss. I haven't tested the port yet, but since newlib has already been ported to many architectures, I would be pretty surprised if there were any major problems. A couple of things I noticed when configuring newlib for