Exupery status

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Exupery status

Michael Latta

What is the status of the Exupery compiler?  Is it being used in 3.9?

 

Michael



Reply | Threaded
Open this post in threaded view
|

Re: Exupery status

Göran Krampe
Hi!

"Michael Latta" <[hidden email]> wrote:
> What is the status of the Exupery compiler?  Is it being used in 3.9?

Bryce will probably answer himself but you can also check out his diary
notes on SqP:

        http://people.squeakfoundation.org/person/willembryce/

...and watch his presentation and read a handout on it:

        http://goran.krampe.se/blog/Squeak/ExuperyTalk2006.rdoc

And no, it is not being used in 3.9. Bryce is using 3.8 as the platform
(don't know if it works as it stands in 3.9). Exupery is an "addon" and
will most probably be an "addon" for a long time, it is simply IMHO not
something that we need to put in an official image - basic or not.

It is also not yet usable for "normal" users, but it can already run
quite a bit of code - and if I understand it right, soon it will be able
to deal with a much larger code base (using blocks and self/super sends
IIRC).

regards, Göran

PS. And oh, please skip HTML in list postings. :)

Reply | Threaded
Open this post in threaded view
|

Exupery status

Bryce Kampjes
In reply to this post by Michael Latta
Michael Latta writes:
 > What is the status of the Exupery compiler?  Is it being used in 3.9?

Exupery is moving forward. I'm finishing up native block compilation
and working on compiling super sends for this release. That should
mean that Exupery will be able to compile most methods. Compiled blocks
work for correct code but don't yet check the number of
arguments. The compiled blocks will also need some work to make them
play nicely with the debugger. They're stable now so long as the
compiled code is bug free and doesn't end up in a debugger.

The release after that will finish off dynamic inlining for primitives
which should help for several common methods including #at: and
#at:put:, @, and new.

That leaves some loose ends and a few more primitives. So I guess
another release or two to be ready for a 1.0.

At that point it would be nice to get Exupery's VM extensions added
to the stock VMs. Then it'll be easy for people to load Exupery from
SqueakMap. I'm hoping for a 1.0 release in the next year.

The next few weeks will be slow, I'm in the process of looking for
another job. My current job is finishing in June.

Bryce