2010/7/29 Eliot Miranda
<eliot.miranda@gmail.com>
Hi Lukas,
On Thu, Jul 29, 2010 at 2:00 AM, Lukas Renggli
<renggli@gmail.com> wrote:
> 1) Cog VM seems to be aimed for x86 and 32 bits. You can read Eliot quotes:
> "The Cog VM is a just-in-time compiler that currently supports only x86
So far I never felt the need for 64-bit images.
> 3) Is it stable for production use?� For example, I read that with seaside
> there are some crashes.
Seaside itself is not the problem, Eliot quickly fixed the remaining
issues with Continuations shortly after the open-source release of
Cog.
and I still need to fix objects-as-methods but have no time right now. �That's probably two to five days work to do right :/
Although it is very important for us, it is not that we needed right NOW. Take all the time you need. It is good to see you want to fix it :)
�
�
The problem are the sockets, they cause frequent random crashes
of the VM.
Do we have any more specific information on these socket-related crashes? �(platform, crash reports, test cases, etc?)
That's the idea of the Pharo OneClick with Cog. We can distribute that so that everybody can start to play with it and report problem.
But for that, we need to know where to get all Cog sources, and how to compile it. In addition, what kind of flags in configure would help you to debug problems and get as much information as possible. With this we can distribute a VM + image that logs as much as possible. This one click would be experimental, not production. Thus, it shouldn't care if it is a little slower (because of the logging).
Cheers
Mariano
�
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project