[Openmcl-devel] Sudden increment in executable image size.
gb at clozure.com
Thu Nov 18 19:54:20 CST 2010
Just to take another stab in the dark: someone (possibly you) was asking
about inline LAP a week or two ago and implied that they were defining
If that was you, is any LAP code involved at the point where things
start getting weird ?
On Thu, 18 Nov 2010, Kaz Kylheku wrote:
> On Thu, 18 Nov 2010 07:21:09 -0800, Kaz Kylheku <kaz at kylheku.com>
>> On Thu, 18 Nov 2010 09:01:29 -0500, Gail Zacharias <gz at clozure.com>
>>> What os version are you on? And what version of the C compiler? I was
>>> seeing a similar problem a while back and it turned out it was a C
>>> compiler bug.
>> I'm using CCL from the release 1.5 tarball, r13651.
> Just fetched the SVN trunk. The problem reproduces.
> I tried with the executable in SVN, and also with a locally rebuilt
> kernel using the latest Cygwin gcc (which I just fetched; I don't have
> devel tools on Cygwin).
> Hmm, Cygwin's "gcc" is 3.4.4. How conservative! GCC 3 was end-of-lifed
> several years ago. At least they could use 3.4.6, the final
> version of gcc 3, sheesh.
> This means that we are all probably using the same compiler for
> building CCL on Windows. The Makefile wants Cygwin, and Cygwin's
> GCC is a sitting duck of a target.
> I will try a different gcc, to test the compiler bug hypothesis.
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel