[LLVMdev] Signals: interpreter vs. JIT

[Nick Lewycky]

Samuel Crow wrote:
> Hello Matt,
> 
> The interpreter doesn't support external functions at all.  This includes the printf function from the glibc library.  That's why the signal causes a segfault.

Yes it does. It always supports atexit, exit, abort, printf, sprintf, 
sscanf, scanf and fprintf. With libffi installed / detected by 
configure, it will be able to call almost any function (there's a TODO 
in there).

Nick

> If you're interested in bringing the interpreter up-to-date with the JIT compiler, I would welcome it since JIT compilation isn't supported on all platforms.
> 
> --Sam
> 
> 
> 
> ----- Original Message ----
>> From: Matt Renzelmann <mjr at cs.wisc.edu>
>> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
>> Sent: Sunday, August 9, 2009 11:23:27 AM
>> Subject: [LLVMdev] Signals: interpreter vs. JIT
>>
>> Just a quick question on LLVM, signals, and the lli interpreter.  A sample
>> program is included at the end.  Platform is x86, Linux, 32-bit, GCC 4.2.4.
>>
>> Does lli -force-interpreter support signals, or is it only the JIT that
>> does?  The following sample program crashes with lli 2.5 and lli
>> top-of-tree.
>>
>> Thanks and regards,
>> Matt
>>
> -snip-
> 
> 
> 
>       
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>