Andy Wingo wi...@pobox.com 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.
On Sun 08 Mar 2009 23:40, Neil Jerram n...@ossau.uklinux.net 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
Hi Andy,
A couple of late comments...
Andy Wingo wi...@pobox.com 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
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. Neil:
Gentlemen, ladies: so long the hack, and so short the time. But the
Creator in her wisdom or absence has given us this moment in which to
ponder the novelties of the VM branch.
Since we last rapped together, let's see:
* One Sunday, I decided that we couldn't honestly claim to have a
Hello!
Andy Wingo wi...@pobox.com 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
-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
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 are now aligned to 8-byte boundaries, and
written in native endianness
Hello Andy!
Thanks for all the good news!
Andy Wingo wi...@pobox.com 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
Hey!
Andy Wingo wi...@pobox.com 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.
Hey hackers,
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.
Otherwise, in the course of
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
¡Hola Andy!
Andy Wingo wi...@pobox.com 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
2009/1/5 Ludovic Courtès l...@gnu.org:
Neil Jerram neiljer...@googlemail.com 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
Hey hey,
On Mon 05 Jan 2009 17:06, l...@gnu.org (Ludovic Courtès) writes:
Neil Jerram neiljer...@googlemail.com 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
Hi Neil,
Neil Jerram neiljer...@googlemail.com 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
Season greetings hackers!
Neil Jerram neiljer...@googlemail.com 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...
Hello,
Andy Wingo wi...@pobox.com 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
Hey Neil,
On Tue 28 Oct 2008 00:51, Neil Jerram neiljer...@googlemail.com writes:
- the principle of the elisp integration is that there is a new value
#nil, which acts as EOL in list contexts, and as #f in boolean
contexts
- as one example of this, the non-VM apply accepts and handles a
2008/12/26 Andy Wingo wi...@pobox.com:
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
Hi Neil,
On Tue 28 Oct 2008 00:51, Neil Jerram [EMAIL PROTECTED] writes:
It's not rocket science, and you probably guessed at that solution
already - but I think it really is the _right_ fix, because
- the principle of the elisp integration is that there is a new value
#nil, which acts as
Hello,
Your friendly neighborhood (oop goops) has been nationalized and
reclaimed by a group calling itself the People's Compilation Front
(PCF). I found the following note scrawled on the back of a page of
R6RS, and wished to communicate it to the wider Guile community. I've
added some comments.
Hi,
Andy Wingo [EMAIL PROTECTED] writes:
I do not think the interpreter / subr division is appropriate for a
multilingual system. To me, the division should be:
* The evaluator / interpreter, that deals in Scheme;
* A layered compiler, with different top-level layers for e.g. Guile,
On Fri 31 Oct 2008 18:54, Andy Wingo [EMAIL PROTECTED] writes:
Granted, we have ideals, and we have tradeoffs, and writing an elisp
compiler. (Then again, maybe not that bad.) If I have to add what I
Meant to say here: writing an elisp compiler might be a bit of work
consider to be a hack to
I've seen `elisp.test' trigger a stack overflow with the interpreter
more often than any other test. Don't know why.
I hacked around this -- see what I've pushed to vm for more info.
I plan to take a look at this after the srfi-18.test hang. (Not that
that should stop anyone else, of
2008/10/16 Andy Wingo [EMAIL PROTECTED]:
* Actually the bit about all of the test suites passing was a lie in
another respect: the elisp test fails, with a C stack overflow,
indicating too much recursion into the interpreter.
I've seen `elisp.test' trigger a stack overflow with the
Hi,
On Thu 16 Oct 2008 07:35, Julian Graham [EMAIL PROTECTED] writes:
My current speculation is that when you compile --with-threads, as I
do, that the socketpair between the signal receiving thread and the
main thread is not closed after the fork, therefore signals in the
child
Hi Andy,
Andy Wingo [EMAIL PROTECTED] writes:
* The VM stack is now marked precisely.
Did you mean stack frame objects that link `program' object invocations?
I guess this stack is referenced by the C stack, so why does something
special need to be done?
* There is a now a debugging
Hi Andy,
My current speculation is that when you compile --with-threads, as I
do, that the socketpair between the signal receiving thread and the
main thread is not closed after the fork, therefore signals in the
child might reach the parent or vice versa, causing random code to
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 random bugs
Heyas,
Since the last update:
* We optimize the (call-with-values producer (lambda (values...) body...)
into a special form to avoid generating the consumer closure. It's
equivalent to:
(receive (values...) producer body).
* Fixed pre-inst-guile not to look at installed paths for
31 matches
Mail list logo
