Hello!
Andy Wingo wi...@pobox.com skribis:
Yes I see what you are saying. It was only recently that things came
together enough to be testable at all (to have the circle between
assembler, linker, and loader). However, the instructions themselves
are fairly well documented; do see
Hello,
Noah Lavine noah.b.lav...@gmail.com skribis:
I sent another email recently about different ways to make the JITter
understand all of the bytecode, but at the time, I thought I would
have to parse the C definition of the VM and generate the JITter from
that in order for it to be merged
On Mon 25 Jun 2012 22:52, l...@gnu.org (Ludovic Courtès) writes:
1) Convert the ELF parser and linker to use symbols instead of the raw
ELF codes, as the DWARF parser does. It's more convenient and not
significantly different, performance-wise.
Yes. The one at
Hello, and happy Solstice! :-)
Andy Wingo wi...@pobox.com skribis:
First of all, I have changed the on-disk format for .go files to be ELF,
even for the old Guile 2.0-style bytecode. This increases the file size
somewhat, though the memory footprint is the same. What it gives us,
though,
Hello,
Seriously though, that seems like a good plan. I wonder what Noah’s
attempts at JITing the 2.0 bytecode would have achieved, though, if we
think of both JIT and the new VM as an “interim solution” before AOT
native compilation.
I can't remember the last email I sent about that, but I
Hi Noah,
Thanks for the thoughts and the hack!
On Sat 23 Jun 2012 16:03, Noah Lavine noah.b.lav...@gmail.com writes:
It looks to me like the GLIL-assembly compiler spends most of its
effort building constant tables, which I believe the RTL assembler
does in the rtl branch.
The other things
Hello,
The new VM looks great.
But after those things are done, we still need to bridge the gap between
Tree-IL and RTL assembly. We will probably have to scrap GLIL, though I
can't tell yet.
As I said, I've been working on a compiler from Tree-IL directly to
RTL. So far, I have not found
Hello all,
A few changes in master and wip-rtl.
First of all, I have changed the on-disk format for .go files to be ELF,
even for the old Guile 2.0-style bytecode. This increases the file size
somewhat, though the memory footprint is the same. What it gives us,
though, is extensibility.
In
