search for: zpu

Displaying 9 results from an estimated 9 matches for "zpu".

Did you mean: cpu
2008 Jun 19
2
[LLVMdev] Backend for the ZPU - a stack based / zero operand CPU
...leased with the resulting code. I did make alterations to the architecture to make it fit GCC without sacrificing CPU size. I have been following llvm.org from a distance, since I finished the GCC backend a couple of years back and there has not really been a reason to build a new compiler for the ZPU. My llvm.org knowledge is ... shallow ... but I'm hoping that someone would find the time & pity to answer my questions: Q: Is a stack based / zero operand CPU and llvm a good match? (GCC wasn't) Q: Should I expect better code density / performance from llvm than GCC for said archite...
2008 Jun 22
1
[LLVMdev] Backend for the ZPU - a stack based / zero operand CPU
On Fri, 20 Jun 2008, [ISO-8859-1] ?yvind Harboe wrote: >> The ZPU has two instructions that I'd also like to use. These instructions >> can push a value from deeper down on the stack and also pop a value >> from the stack and store them deeper down on the stack. > > Sounds like the Intel X87 floating point stack, which we support. GCC does...
2010 Nov 18
0
[LLVMdev] Writing a backend for the ZPU
Hi, I'm trying to have another stab at writing an LLVM ZPU backend. Any pointers or encouragement would be greatly appreciated. So far I've been wandering around the LLVM trying to read up and I've hacked together something that builds just to experiment and get a feel for the build system. I was able to write a backend for GCC which has been in...
2008 Jun 20
1
[LLVMdev] Backend for the ZPU - a stack based / zero operand CPU
...is relatively easy to do custom code > generation phases. For example, you probably don't want to run the > register allocator at all. Not to run the register allocator would definitely be nice and probably be a better match. It seems like you're implying that llvm uses trees. The ZPU has two instructions that I'd also like to use. These instructions can push a value from deeper down on the stack and also pop a value from the stack and store them deeper down on the stack. Calling convention was very tricky w/GCC since the ZPU only has SP & PC. There are no registers to...
2010 Nov 19
0
[LLVMdev] Fw: Writing a backend for the ZPU
Whoops! Forgot to CC: the list! ----- Forwarded Message ----- > From:Samuel Crow <samuraileumas at yahoo.com> > To:Øyvind Harboe <oyvind.harboe at zylin.com> > Cc: > Sent:Thursday, November 18, 2010 7:22:39 PM > Subject:Re: [LLVMdev] Writing a backend for the ZPU > > > Hello, Some > thoughts/problems: - In GCC I created > registers which were just stack > slots in the stack frame. This > allowed the reload and register allocation > to do it's thing. What > kind pre-stackifier register file do I define for > the...
2008 Jun 23
0
[LLVMdev] Backend for the ZPU - a stack based / zero operand CPU
> We mean ZPU looks like x86 fp stack. We handle it by register > allocating it like a normal register based cpu than add a x87 > stackifer pass to convert it to stack operations. Thanks! > You do not have to. Take a look at PPC and ARM branch fix up passes. > llvm backends compute exact length of...
2008 Nov 21
1
[LLVMdev] Simple stack machine
Hi all, we're looking around a bit for a small and simple stack-based architecture, that we could use as a sidekick to the DSP processor we are developing. We've been looking at ZPU for a bit, but are also considering developing our own hardware for this (possibly very much tuned to LLVM). Of course, that would also mean building an LLVM backend. I guess having a very simple backend would also server LLVM well, as an example backend and one to base new architectures on. Now,...
2009 Jul 23
1
[PATCH server] changes required for fedora rawhide inclusion.
...zJ4(!$L=;FB*}6<KR74zFQXPh at TOm3zBZ^ZbfE1V2g05O at 0^EQUE1oJc(=J8?4J!`O zSb9=pnpIl#Ocz`kCXwixRYV6;GDRfwe~c)Z|0Qp<;^;u#BH}jxm4BkM_%3CMNLCyV z;oL at U%|b#rQkI${Gt;3sh|{TL3;yg_w^ThdisS!?-bBm}5yHivZk0%}LP5<*7JW34 zFjW_iG&*@CPDIhdYJ5WE<XW6GX@(P;OpQzEI&I=mF<{N<BmhmM<?#QX6j3O(ZpuKa zKr;G&sk0I3%gI-D>i8cOR<pHM_9!nIIf&bBXNfq`n?`f<<H^lLB8HmA%|?PMBrWRZ zg1Nc1v at TkzEt2LxDWY5I+!CX~ytIst+3c|pm?Mhx-- at AFu1(A()(RoArc0>9QE;i^ zpe~ow>BgUI!a-cFgsx`BcdXHMtu(rbqxu^y6JJ>QZBvjT2pNsCNK=&>zuxsYW>a4r zmLez1ohX;tw)WQz?tf)#<Nn;bqg8Gup_!Qse~_o!`Xl-!G1...
2013 Jul 31
29
[PATCH 0/9] tools: remove or disable old/useless/unused/unmainted stuff
depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *