Re: use of c ellipsis

[Mateusz Czaplinski <czapkofan@...>]

Don't know of easier solution unfortunately, but for Lua 5.1:

$ grep -h -I -o -P '(luaO_pushfstring|luaG_runerror|luaL_error|lua_pushfstring).*' * | sed 's/"[^"]*"/""/g' | sort | uniq | wc -l
77

Not very few, but not that much either. Depending on how strong is your inclination, may still be analyzable. (I did some similar kind of stuff, and of similar size, for my goluago project. Also, for me, writing small Lua scripts for automating some of the work (during both analysis & conversion) in quick & hackish way can sometimes reduce the boring part of the effort, and even make it fun. YMMV, obviously.)

cheers

/Mateusz Czapliński.

On Wed, Feb 26, 2014 at 4:40 AM, Jim Rambo <jrambo316@yahoo.com> wrote:

nvidia nvcc for compiling device code on geoforce gtx 660.  Pretty modern actually.

It "mostly" supports c99 supposedly.  It supports printf in recent versions using "...", but does not allow in device code.

It seems to recognize the va_list, va_arg, va_start, va_end, BUT not "...".

I wanted to see if I could play with lua on this device along the lines of eLua.

It looks like I am stymied by the stupid ellipsis!  It looks to be a big pain to try and hard code a max number of parameters in lua base as the ellipsis seems to be used all over.

I am attempting a workaround in that portion of the code by substituting in PTX but no dice so far.

Jim

On Tuesday, February 25, 2014 9:06 PM, Sean Conner <sean@conman.org> wrote:

It was thus said that the Great Jim Rambo once stated:

> Hello,
>
> I am trying to port lua to another architecture that is basically ansi c. 
> However, the ellipsis is not supported.  I cut out all the extra libraries
> but have even found that the ellipsis is used in the core.
>
> Any ideas?  The remaining obstacle seems to be centered around the various
> pushstring functions.

  What compiler and system?  Because that must be one very old compiler you
are using, if it doesn't support the ANSI C vararg feature ...

  -spc