[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: build optimizations
- From: Rob Kendrick <rjek@...>
- Date: Tue, 22 Mar 2011 13:15:43 +0000
On Tue, Mar 22, 2011 at 01:50:06PM +0100, Mike Pall wrote:
> > 2. The file all.c (aka one.c) allows Lua to be built as a single object file,
> > and allows the compiler to generate better code and with just the Lua API
> > as public symbols. We are considering building Lua in this way, so that
> > liblua.a will consist of a single object file. Does anyone see a drawback
> > to this?
>
> This will prevent anyone from building Lua in a memory-limited
> environment.
>
> E.g. the "make amalg" target of LuaJIT needs around 200-300 MB of
> memory for GCC. That's why it's not the default. Yeah, I know
> that's not much these days.
This could easily be a problem for us; some of our ARM build boxes only
have 128 or 256MB of RAM. (Although we're slowly replacing them with
noticably stouter machines, it'd still be a problem.)
B.