chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] Re: compiling jbogenturfa'i .scm => .c takes 2.5 hou


From: Alan Post
Subject: Re: [Chicken-users] Re: compiling jbogenturfa'i .scm => .c takes 2.5 hours
Date: Sat, 27 Nov 2010 09:12:01 -0700

On Sat, Nov 27, 2010 at 04:05:01PM +0100, Felix wrote:
> From: Alan Post <address@hidden>
> Subject: [Chicken-users] Re: compiling jbogenturfa'i .scm => .c takes 2.5 
> hours
> Date: Fri, 26 Nov 2010 15:16:54 -0700
> 
> > 
> > I would love to better understand what it is I'm doing and why it is
> > causing a problem.  I'm not sure how to fix my code, as I don't
> > quite get why what I'm doing is triggering the compiler to generate
> > such large files.
> 
> Alan, if you use "-debug 2", the compiler will output the result of
> the macro-expansion, which may be helpful in looking at the code
> your macros generate. Somewhere excessive code is generated, which
> may be less costly in the interpreter due to sharing of subexpressions.
> 

I left a build running last night with no ulimit (I keep a login
class on my machine for such purposes called bigjob, which I originally
had because I was sorting huge files and running out of memory.), and I
did, in theory, get a .so file:

9622780 jbogenturfahi.so

It turns out I do have one other .so file larger than this on my machine
already, but wow!  I'm glad to know I can compile this code.  I'm kicking
off another build now with "-debug 2" and I'll report later today.

Thank you Felix.  I'm scared by this problem, as I fear I've made
some fundamental architecture choice that I'm now having to
accomodate or refactor.

-Alan
-- 
.i ko djuno fi le do sevzi



reply via email to

[Prev in Thread] Current Thread [Next in Thread]