Displaying 13 results from an estimated 13 matches for "disablesymbolsearch".
2012 Nov 25
2
[LLVMdev] MCJIT and Lazy Function Creators
Out of curiosity, I'm replacing the JIT with MCJIT on my compiler. As
all "external" functions are provided by the language's FFI mechanism,
it does
MyExecutionEngine->DisableSymbolSearching();
MyExecutionEngine->InstallLazyFunctionCreator(&MyLazyFunctionCreator);
which works fine with the JIT. However, MCJIT insists on resolving
unknown symbols by searching them outdoors and seems oblivious of the
existence of MyLazyFunctionCreator.
Is this a bug?
Is there a workaround, o...
2009 Jun 05
4
[LLVMdev] How to stop symbol searching without aborting
...with the LLVM JIT.
It is very important that the driver does not have access to any other
function in the application except those I provide. It's not OK for
our application to abort if a driver calls an undefined function - I
want to just disable _that driver_ in that event.
I can use DisableSymbolSearching() but that causes application to
abort for unknown symbols.
Please advice!
/Marcus
2009 Oct 16
3
[LLVMdev] MallocInst/CallInst bitcast,
On Oct 16, 2009, at 4:43 AM, Daniel Waterworth wrote:
> Never mind, I used ExecutionEngine's InstallLazyFunctionCreator and
> DisableSymbolSearching to cause malloc and free calls to be handled
> by my logging functions. Sorry for the unnecessary list mail.
No problem, this is a better way to go. The MallocInst and FreeInst
instructions are about to be removed from LLVM IR. Malloc and free
will be represented normal 'call'...
2009 Oct 16
0
[LLVMdev] MallocInst/CallInst bitcast,
Never mind, I used ExecutionEngine's InstallLazyFunctionCreator and
DisableSymbolSearching to cause malloc and free calls to be handled by my
logging functions. Sorry for the unnecessary list mail.
Is it possible to find out the size and beginning pointer of the current
stack frame, from a function operating outside of the virtual machine, but
called by a function within it?
Thanks,...
2012 Nov 27
0
[LLVMdev] MCJIT and Lazy Function Creators
Óscar Fuentes <ofv at wanadoo.es> writes:
> Out of curiosity, I'm replacing the JIT with MCJIT on my compiler. As
> all "external" functions are provided by the language's FFI mechanism,
> it does
>
> MyExecutionEngine->DisableSymbolSearching();
> MyExecutionEngine->InstallLazyFunctionCreator(&MyLazyFunctionCreator);
>
> which works fine with the JIT. However, MCJIT insists on resolving
> unknown symbols by searching them outdoors and seems oblivious of the
> existence of MyLazyFunctionCreator.
>
> Is this...
2009 Oct 16
2
[LLVMdev] MallocInst/CallInst bitcast,
Hello,
I'm writing a virtual machine that functions as a sandbox based on llvm. In
order to prevent programs from accessing memory that has not been allocated
to them, I want to replace calls to malloc and free with calls to a logged
functions that will record the memory that is being allocated to the
program. Is it possible to cast/convert a MallocInst or FreeInst to a
CallInst?
Thanks,
2009 Jun 05
1
[LLVMdev] How to stop
...with the LLVM JIT.
It is very important that the driver does not have access to any other
function in the application except those I provide. It's not OK for
our application to abort if a driver calls an undefined function - I
want to just disable _that driver_ in that event.
I can use DisableSymbolSearching() but that causes application to
abort for unknown symbols.
Please advice!
/Marcus
2009 Jun 08
0
[LLVMdev] How to stop symbol searching without aborting
...t; It is very important that the driver does not have access to any other
> function in the application except those I provide. It's not OK for
> our application to abort if a driver calls an undefined function - I
> want to just disable _that driver_ in that event.
>
> I can use DisableSymbolSearching() but that causes application to
> abort for unknown symbols.
>
>
> Please advice!
>
>
> /Marcus
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/m...
2009 Oct 16
0
[LLVMdev] MallocInst/CallInst bitcast,
...amp;a);
}
Preferably one which isn't destroyed by optimization.
Thanks again,
Daniel
2009/10/16 Chris Lattner <clattner at apple.com>
>
> On Oct 16, 2009, at 4:43 AM, Daniel Waterworth wrote:
>
> Never mind, I used ExecutionEngine's InstallLazyFunctionCreator and
> DisableSymbolSearching to cause malloc and free calls to be handled by my
> logging functions. Sorry for the unnecessary list mail.
>
>
> No problem, this is a better way to go. The MallocInst and FreeInst
> instructions are about to be removed from LLVM IR. Malloc and free will be
> represented no...
2009 Jun 05
0
[LLVMdev] How to stop symbol searching without aborting
...is very important that the driver does not have access to any other
> function in the application except those I provide. It's not OK for
> our application to abort if a driver calls an undefined function - I
> want to just disable _that driver_ in that event.
>
> I can use DisableSymbolSearching() but that causes application to
> abort for unknown symbols.
An LLVM program can call any address, valid or not. If the programmer
figures out the address of one of those "forbidden" functions, he can
call it. You may write some pass for detecting suspicious constructs and
rejec...
2009 Jun 08
1
[LLVMdev] How to stop symbol searching without aborting
...e driver does not have access to any
>> other
>> function in the application except those I provide. It's not OK for
>> our application to abort if a driver calls an undefined function - I
>> want to just disable _that driver_ in that event.
>>
>> I can use DisableSymbolSearching() but that causes application to
>> abort for unknown symbols.
>>
>>
>> Please advice!
>>
>>
>> /Marcus
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs....
2012 Nov 27
2
[LLVMdev] MCJIT and Lazy Function Creators
...MCJIT and Lazy Function Creators
Óscar Fuentes <ofv at wanadoo.es> writes:
> Out of curiosity, I'm replacing the JIT with MCJIT on my compiler. As
> all "external" functions are provided by the language's FFI mechanism,
> it does
>
> MyExecutionEngine->DisableSymbolSearching();
> MyExecutionEngine->InstallLazyFunctionCreator(&MyLazyFunctionCreator);
>
> which works fine with the JIT. However, MCJIT insists on resolving
> unknown symbols by searching them outdoors and seems oblivious of the
> existence of MyLazyFunctionCreator.
>
> Is th...
2010 Nov 13
8
[LLVMdev] Ahoy JIT Users
Hi,
I am starting to poke at the LLVM JIT, which seems to be in need of some TLC.
If you are a "sophisticated" JIT user and are using either internal
APIs (either by integrating with LLVM, or by other C++ tricks), or are
using obscure or poorly documented public APIs (e.g., why is
runJITOnFunction exposed?) please make me aware of it!
I reserve the right to break anything which