http://c9x.me/compile/
Getting it to generate machine code is almost trivial.
Porting it to ARM is only reasonably complicated.
It is *very* fast.
I will refactor it a bit and work more on it starting
mid-september. Feel free to join the force.
On Sat, Jun 18, 2016 at 10:33:23AM +0100, Connor L
How about QBE, which is one step up from assembly?
If you don't want to use Lua, what about doing something more like CGI? Then
you can just call the configuration program with what you want a dynamic answer
for. You could then have a simple awk script parse your config file and answer
queries to the host program.
I suggest this because I have
C JIT->have a look at tinycc from F. Bellard.
llvm is c++ then, by definition is not suckless and a massive brain damaged
kludged.
cheers,
--
Sylvain
There's several examples of P-code/Pascal VMs around [0][1][2][3].
Some more detailed than others.
[0] https://en.wikipedia.org/wiki/P-code_machine#Example_machine
[1] http://www.icodeguru.com/vc/10book/books/book4/secg.htm
[2] http://blackmesatech.com/2011/12/pl0/pl0.xhtml
[3] https://github.com
On Sat, 18 Jun 2016, Connor Lane Smith wrote:
> Hi all,
>
> I was wondering if others had an opinion on JIT. Suppose we don't need
> anything fancy like adaptive optimisation, but just wanted to compile
> a program at runtime. One possibility might be to generate C code and
> store that in a file
On Sat, Jun 18, 2016 at 10:33:23AM +0100, Connor Lane Smith wrote:
> Hi all,
>
> I was wondering if others had an opinion on JIT. Suppose we don't need
> anything fancy like adaptive optimisation, but just wanted to compile
> a program at runtime.
Why?
Hi all,
I was wondering if others had an opinion on JIT. Suppose we don't need
anything fancy like adaptive optimisation, but just wanted to compile
a program at runtime. One possibility might be to generate C code and
store that in a file and then call the C compiler and then execute the
resultin
