Andy Wingo writes:
>> How much of this is compiler-specific? Does some of it also apply to
>> old-style reading and interpreting?
>
> No, it's just compiler-specific. The reader captures source information
> at when it reads lists, as you know, and this is just propagating more
> of it.
OK, tha
Hi Neil,
On Sun 08 Mar 2009 12:49, Neil Jerram writes:
> Andy Wingo writes:
>
>> * Much more source information propagates through the compiler and
>> into the metadata now.
>
> How much of this is compiler-specific? Does some of it also apply to
> old-style reading and interpreting?
No
On Sun 08 Mar 2009 23:40, Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>>> Anyway, that's where I am. Bug-wise we still have a bug in backtraces,
>>> which I need to pin down at some point, and update docs -- but generally
>>> speaking we're mergeable. What do people think, shou
l...@gnu.org (Ludovic Courtès) writes:
>> Anyway, that's where I am. Bug-wise we still have a bug in backtraces,
>> which I need to pin down at some point, and update docs -- but generally
>> speaking we're mergeable. What do people think, should I be working on
>> master at some point?
>
> Sure.
Hi Andy,
A couple of late comments...
Andy Wingo writes:
> * Much more source information propagates through the compiler and
> into the metadata now. In short, whereas before it was "expressions
> are only marked as coming from a source location if they are eq? to
> an expression
Hello!
Andy Wingo writes:
> * I've started to think about optimization, and what's clear is that
> GHIL as it stands is too much of a pain in the ass -- you can't turn
> a ((lambda ...) ...) into a (let ... ...) without like 30 lines of
> code. I decided that having alpha-renamed v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Wingo wrote:
> Greets!
>
> So, yes, it's Saturday night: but I do love Guile hacking so. (Also: my
> partner is away.) So a VM status update it is!
>
> * The parts of the instruction stream that are mapped directly to
> "struct scm_objcode
Andy Wingo writes:
>> Is that the kind of thing that you had in mind, or have I missed your
>> point?
>
> You've got it :)
Hooray!
> I think that selfishly, I need to implement another language if I'd like
> to present something about "guile's multilingual framework", or else I'd
> be laughed o
On Wed 04 Feb 2009 00:34, Neil Jerram writes:
> [Translation via decompilation] sounds interesting. But it sounds more
> like something educational to me, rather than a solution to the
> original translation desire.
You're right. But it's neat, though!
> Is that the kind of thing that you had i
Andy Wingo writes:
> * Just as we have a tower compilers (and thus languages), we now have a
>tower of /decompilers/. Currently I've only implemented
>value->objcode (only valid for values of type program or objcode),
>objcode->bytecode, and bytecode->assembly, but it's possible to
>
Hello Andy!
Thanks for all the good news!
Andy Wingo writes:
> * I think there's something publishable in all of this language tower
> business, but I'd need a convincing second high-level language. I
> think JavaScript is the right one. We need to write a compiler to
> GHIL, and
Hey!
Andy Wingo writes:
> I just finished up a lot of typing at the manual, and I hope I'm done
> with that. The net result is that the VM is documented quite thoroughly,
> and the compiler as well. I'll send those documents to the list in
> separate mails for inline comments.
Great!
> I had a
¡Hola Andy!
Andy Wingo writes:
> So, ahem, what I mean to say is that the small number of tests reflects
> the small number of bugs, or something? ;-)
You might be right. :-)
> Sure, and at some point I'll switch to benchmarking and optimization --
> but in the meantime perhaps someone whose
Hi!
On Mon 05 Jan 2009 22:03, l...@gnu.org (Ludovic Courtès) writes:
> I think it's good to have unit tests for the compiler/VM too.
Sure, would be good. First I'm going to work on documenting the
compiler though, so there's something to test. But honestly speaking,
I'm not going to go on a spre
Hello,
Andy Wingo writes:
> Well, there are larger tests, in that the normal test suite passes with
> VM-compiled code (e.g. ice-9 and all that).
Yes, I remember reading that (and that is reassuring!), but I think it's
good to have unit tests for the compiler/VM too.
> And there are smaller te
Hi Neil,
"Neil Jerram" writes:
> I meant commits like this one:
> http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=9320e9339085b4d004c255eb55619819fe0b3ca2.
>
> Another bigger example, by me, is
> http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=69986e21d30b85bd0b4fd7e81cd24c
Hey hey,
On Mon 05 Jan 2009 17:06, l...@gnu.org (Ludovic Courtès) writes:
> "Neil Jerram" writes:
>
>> Nice. Regarding the merge to master, though,
>>
>> - I think that would imply that the VM is included in the next release
>> series (1.10.x or 2.0.x); is that your intention? (I have no
>> ob
2009/1/5 Ludovic Courtès :
>
> "Neil Jerram" writes:
>
>> Nice. Regarding the merge to master, though,
>>
>> - I think that would imply that the VM is included in the next release
>> series (1.10.x or 2.0.x); is that your intention? (I have no
>> objection!)
>
> No objection either, but... some
Season greetings hackers!
"Neil Jerram" writes:
> Nice. Regarding the merge to master, though,
>
> - I think that would imply that the VM is included in the next release
> series (1.10.x or 2.0.x); is that your intention? (I have no
> objection!)
No objection either, but... some benchmarking
2008/12/26 Andy Wingo :
> Happy St. Stephen's Day, hackers of the good hack!
More eating the good pie than hacking the good hack right now!
> I just landed a few patches on the vm branch that integrate backtrace
> handling between the interpreter and the VM. `save-stack' saves the VM
> stack and
On Mon 29 Sep 2008 09:35, [EMAIL PROTECTED] (Ludovic Courtès) writes:
> Hi!
>
> Andy Wingo <[EMAIL PROTECTED]> writes:
>
>> Current plan is to either look at that GC leak, if I'm feeling
>> adventurous, or otherwise keep plugging away at the test suite. Most
>> things pass but I do find some rando
Hi!
Andy Wingo <[EMAIL PROTECTED]> writes:
> I'm not happy about one thing though, a GC leak that I found and had to
> paper over. You'll see it if you look at gitk origin/vm.
>
> Current plan is to either look at that GC leak, if I'm feeling
> adventurous, or otherwise keep plugging away at the
22 matches
Mail list logo
