Hi Blake,

On Sat, Nov 6, 2010 at 7:06 PM, Blake McBride blake@mcbride.name wrote:

What about the issue I hear about large modules having trouble compiling?  I think this is an issue that seems to have been recently added.  What is the status of that?

Thanks for picking up on the mail!

Checking the logs, it seems the issue has been added ~ 5 months ago when we started to use less reflection to load our FASL-embedded classes. The system loads a bootstrapping class through reflection.

From there, all classes are loaded through normal 'new' calls, saving

us the slowness of (stack) security access controls that come with reflection.

The problem with the current system is that it generates a single method, no matter how many classes need to be instantiated. However, if a FASL contains many many function classes, all the instantiations don't fit into a single method (64kB). To resolve this issue I guess all that needs to happen is to split up the generated code in enough methods to keep them all below 64kB.

The issue hasn't been addressed yet.

Bye,

Erik.

On Thu, Nov 4, 2010 at 3:03 PM, Erik Huelsmann ehuels@gmail.com wrote:

...

We've had a productive number of weeks since our last release. Changes include:

* Running the Maxima test suite without failure [Thanks to the Maxima team for their part in this!]  * CLOS thread safety fixes  * Fixes to be able to run on Oracle JRockit JVM  * Numerous tickets fixed  * A new class file writer to build further optimizations upon

So, I think we should be moving toward a release real soon now. Is there more to be added to trunk? If not, I'll be branching by the end of the weekend; otherwise, let's discuss and see what timelines to set.

Everybody, thanks again for your contributions!

Bye,

Erik.

---

armedbear-devel mailing list armedbear-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel