Displaying 3 results from an estimated 3 matches for "heceforth".
Did you mean:
henceforth
2010 Jul 07
2
[LLVMdev] Another way to JIT: "dlopen from memory"
...nd of way
> - dylib's can have debug information generated in the standard way
> - no need to manage memory chunks for JIT'd code
This idea has been kicked around a few times on IRC and elsewhere, and
I think it's pretty clever. The idea is to JIT by making a valid
dylib/dll/so (heceforth, dylib) with the JITed code in memory, and
then convincing the loader to load it. This is nice for the reasons
listed above.
I think it would be neat if LLVM could package up this functionality,
since it fits most use cases for the current LLVM JIT. LLVM
compilation is already heavyweight, so th...
2010 Jul 07
0
[LLVMdev] Another way to JIT: "dlopen from memory"
...39;s can have debug information generated in the standard way
>> - no need to manage memory chunks for JIT'd code
>
> This idea has been kicked around a few times on IRC and elsewhere, and
> I think it's pretty clever. The idea is to JIT by making a valid
> dylib/dll/so (heceforth, dylib) with the JITed code in memory, and
> then convincing the loader to load it. This is nice for the reasons
> listed above.
>
> I think it would be neat if LLVM could package up this functionality,
> since it fits most use cases for the current LLVM JIT. LLVM
> compilation...
2010 Jul 07
1
[LLVMdev] Another way to JIT: "dlopen from memory"
...information generated in the standard way
>>> - no need to manage memory chunks for JIT'd code
>>
>> This idea has been kicked around a few times on IRC and elsewhere, and
>> I think it's pretty clever. The idea is to JIT by making a valid
>> dylib/dll/so (heceforth, dylib) with the JITed code in memory, and
>> then convincing the loader to load it. This is nice for the reasons
>> listed above.
>>
>> I think it would be neat if LLVM could package up this functionality,
>> since it fits most use cases for the current LLVM JIT. LL...