search for: sweet16

Displaying 5 results from an estimated 5 matches for "sweet16".

Did you mean: sweet
2014 Jul 04
2
[LLVMdev] MOS6502 target
...#39;s worse than, say, Thumb2, due to the lack of registers. On 16 or > 32 bit values it's diabolical if everything is done inline. > > Wozniak's "Sweet 16" is still not a terrible design for this, but I think > a bit more thought can come up with something better. The Sweet16 > interpreter is pretty small though (under 512 bytes I think?), which is > pretty important. > > http://www.6502.org/source/interpreters/sweet16.htm > > The criteria whether to use native or bytecode for a given function is > pretty similar to the inlining decision. And a dece...
2014 Jul 04
2
[LLVMdev] MOS6502 target
Well, the stack pointer be a single byte, so pushing things on there doesn't work terribly well. Assuming I pass by reference, that's 128 values absolutely total before it wraps around and silently clobbers itself. It means single byte values will be incredibly inefficient... Tricky stuff. I'm lucky on the C64 since it's rare to exit back to the kernel with machine language apps
2016 Feb 12
3
Experimental 6502 backend; memory operand folding problem
Greetings, LLVM devs, For the past few weeks, I have been putting together a 6502 backend for LLVM. The 6502 and its derivatives, of course, have powered countless microcomputers, game consoles and arcade machines over the past 40 years. The backend is just an experimental hobby project right now. The code is available here: <https://github.com/beholdnec/llvm-m6502>. This branch introduces
2018 Dec 17
2
LLVM Backend for a platform with no (normal) stack
Not only do FPGAs not support recursion, we don’t even support calls! All user code must be inlined into one kernel/component, which is then used to create HDL for the FPGA. Mark From: Bruce Hoult <brucehoult at sifive.com> Sent: December 17, 2018 9:28 AM To: Mendell, Mark P <mark.p.mendell at intel.com> Cc: jjones at prc-hsv.com; LLVM Developers Mailing List <llvm-dev at
2016 Feb 13
4
Register spilling fix for experimental 6502 backend
So I've been designing an experimental 6502 backend for LLVM. Link: <https://github.com/beholdnec/llvm-m6502> The 6502 only has a few registers, one accumulator and two indexes, none of which are large enough to hold an absolute pointer. Because of this, the backend really tests the power of LLVM's register allocator (RA). I've made a change to the RA that might be of interest