[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Lua Cross Compiler
- From: Asko Kauppi <askok@...>
- Date: Fri, 4 Apr 2008 11:04:45 +0300
How about just defining LUA_INTEGER to be 'int' (not ptrdiff_t) on the
That would make lua_Integer go 32-bit, which should be enough for full
bytecode compatibility. Am I right?
Use of 'ptrdiff_t' is anyways a bit troublesome, and mostly useful in
the 16/32 bit architectures.
Steven Barth kirjoitti 4.4.2008 kello 10:33:
Precompiling does not imply reduction in size. Stripping debug
helps reducing size but of course gets you less information in case
errors. I think you'd be better off compressing instead of
See http://lua-users.org/lists/lua-l/2003-05/msg00380.html and that
Compression is a nice idea here but our filesystem on these devices
uses LZMA-compression so we would not really benefit from this.
But more disk space for less debugging information is a good
this case. And this remembers me of another point I forgot to
CPU time we would save by byte-compiling the Lua files.
So my question is: Is there anything which could be helpful for
compiling Lua byte-code
The easiest path is to change lundump.c to handle the multiple
especially if the differences are minor. How different are your
Our target platforms (the important ones) are all 32bit ones but
byte-orders but on of our main compiling platforms is amd64 so we
this 64bit integer problem.
But thank you all for your replies I will have a look into the
give it a try.