[Gcl-devel] Re: GCL profiling with ACL2

2005-03-22 Thread Camm Maguire
Greetings! si::*system-directory* is used in a number of places, all with the central purpose of trying to find files that should be present in a GCL installation. As GCL's general portable design is to allow images to work where there is no such installation, it might not make sense for ACL2 to

[Gcl-devel] Re: GCL profiling with ACL2

2005-03-22 Thread dshardin
Camm Maguire [EMAIL PROTECTED] wrote: 2) Always toggle the init_ name, and expand our currently crude translation to ensure that we always come up with a valid C identifier. (Right now, we only translate - to _) Would that solve David Hardin's problem, as follows? Yes. If

[Gcl-devel] Re: Call for help with MACOSX Re: [Axiom-developer] [MACOSX] What is unexec and why does it fail ?

2005-03-22 Thread Aurelien Chanudet
Beyond the axiom issue discussed below, some acl2 users at the University of Texas are running into difficulties with the mac code when making very large images. Would you have a chance to try to build ACL2 with maxpages doubled, quadrupled, and even multiplied by 8 if you OS allows?