minor updates

lua-5.3.0-tests/all.lua

@@ -148,7 +148,7 @@ report"gc.lua"
 local f = assert(loadfile('gc.lua'))
 f()
 
-if not ravi.auto() then
+if not ravi or not ravi.auto() then
   dofile('db.lua')
 end
 assert(dofile('calls.lua') == deep and deep)
@@ -175,7 +175,7 @@ dofile('vararg.lua')
 dofile('closure.lua')
 dofile('coroutine.lua')
 dofile('goto.lua', true)
-if not ravi.auto() then
+if not ravi or not ravi.auto() then
   dofile('errors.lua')
 end
 dofile('math.lua')

lua-5.3.0-tests/pm.lua

@@ -108,7 +108,7 @@ local function range (i, j)
   end
 end
 
-if not ravi.auto() then
+if not ravi or not ravi.auto() then
   local abc = string.char(range(0, 255));
 
   assert(string.len(abc) == 256)

readthedocs/index.rst

@@ -22,6 +22,7 @@ Contents:
    llvm-tbaa
    ravi-benchmarks
    ravi-jit-status
+   ravi-jit-libgccjit
 
 
 Indices and tables

readthedocs/ravi-jit-libgccjit.rst

@@ -0,0 +1,21 @@
+========================================
+JIT Compilation for Ravi using libgccjit
+========================================
+
+Introduction
+------------
+The latest `gcc 5.1 release <http://gcc.gnu.org/>`_ contains a new component called ``libgccjit``. This basically exposes an API via a shared library to the compilation functions within gcc. 
+
+I am keen to provide support for this in Ravi. From initial look it seems to contain all the features I need to implement a JIT compiler for Ravi. Obviously having implemented the LLVM version it is going to be a little easier as I can mostly do a port of the LLVM version.
+
+License
+-------
+Ravi with this component will be licensed as GPLv3. Without this component the license will be MIT license.
+
+Why another JIT engine?
+-----------------------
+Well partly as I feel I have a moral obligation to support gcc, given it has been instrumental in bringing about the OpenSource / Free Software ecosystem. 
+
+Secondly I am always looking for alternatives that will let me reduce the footprint of Ravi. The libgccjit is offered as a shared library - this is a great thing. I hate to have to statically link LLVM. 
+
+LLVM implementation and libgccjit implementation will both be kept in sync so that user can choose either option. 

readthedocs/ravi-jit-overview.rst

@@ -1,5 +0,0 @@
-========================
-JIT Compilation for Ravi
-========================
-
-Moved to ravi-jit-status.rst