libgccjit 5.2 on Mac OSX Yosemite

[Dibyendu Majumdar]

On 14 August 2015 at 02:38, David Malcolm <dmalcolm@redhat.com> wrote:
> Out of interest, how does this compare to LLVM.  IIRC you had said
> libgccjit was taking about 5x longer than LLVM; is that still the case?
>
>> Interpreted mode:
>>
>> test done on 13/08/2015, at 21:23:43
>> Lua 5.3
>> 64-bit integers, 64-bit floats
>> cleaning all!!!!
>> ......    ---- total memory: 60.0K, max memory: 2.7M ----
>> total time: 0.57s (wall time: 1s)
>>
>>
>> JIT mode:
>> testing date/time
>> test done on 13/08/2015, at 21:51:11
>> Lua 5.3
>> 64-bit integers, 64-bit floats
>> cleaning all!!!!
>> ......    ---- total memory: 59.9K, max memory: 2.7M ----
>> total time: 659.17s (wall time: 1648s)
>

LLVM 3.7 branch on same hardware and OS:

test done on 14/08/2015, at 21:49:47
Lua 5.3
64-bit integers, 64-bit floats
cleaning all!!!!
......    ---- total memory: 59.9K, max memory: 2.2M ----
total time: 149.18s (wall time: 151s)

Note that the LLVM version handles a few more byte codes so this would
be a disadvantage to LLVM as it will compile more functions.

With libgccjit you can literally watch the processes being invoked -
as, collect2, ld, etc. - as the OS X terminal shows any subprocesses
launched in the title bar.

On my other environment which is running Ubuntu as a VM under Windows,
the difference is less as that environment has SSD disks so that helps
libgccjit.

Regards
Dibyendu