Stuff to include in libgccjit 5.2

[Dibyendu Majumdar]

On 30 June 2015 at 20:53, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
> Hi Dave,
>
> Realise the deadline for 5.2 is close, but just wanted to let you know
> that as I compile bytecodes I tend to run standard Lua test suite. I
> am finding that the test suite fails at present. This could be due to
> bugs in my code or bugs in libgccjit - it takes me some time to
> isolate each issue into a small test case and then debug. In an ideal
> world I would like to complete the implementation of all the major
> bytecodes (at least to a level currently implemented in LLVM), and be
> able to successfully run all tests. It would then be nice if I
> discover any libgccjit bugs then the fixes for these to be included in
> 5.2. But not sure whether all this is possible before the 5.2
> deadline.
>

Pleased to report that the test suite is now working for the bytecodes
implemented so far. The bugs were all related to missing evaluations
of function call expressions. This is the most frequent mistake I am
making when porting LLVM code - in LLVM of course everything is
immediate - whereas in libgccjit one has to remember that an rvalue is
not evaluated unless it is used in a call or another expression.

I will try to implement as many op codes as I can over the weekend and
report back in case of issues.

Thanks and Regards

Dibyendu