Re: build optimizations

[Mike Pall <mikelu-1103@...>]

Luiz Henrique de Figueiredo wrote:
>    but a Lua library compiled with -fomit-frame-pointer might not
>    be debuggable.

Nothing prevents you from using -fomit-frame-pointer and -g
together. Modern debuggers don't rely on frame pointers, anyway.

[Note that -fomit-frame-pointer is implied by -O2 on all CPUs,
except for x86, anyway.]

> 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.

--Mike