Displaying 4 results from an estimated 4 matches for "createx86objectcodeemitterpass".
2009 Jul 16
3
[LLVMdev] [patch] CodeEmitter Memory Foot Reduction
...ty.
>
> Hi Aaron,
>
> I'm sorry for not getting back to you sooner. I work fairly LIFO
> and the craziness that has happened since your emails have
> distracted me.
>
> One problem with this patch is that (for example)
> X86TargetMachine.cpp refers to the "createX86ObjectCodeEmitterPass"
> symbol, which forces the code emitter to object code emitter to be
> linked into the X86 target module. There is still no way to create
> a JIT without two copies of the code emitter template. I believe
> that aligning this work with Daniels work to make the targets mo...
2009 Jul 16
0
[LLVMdev] [patch] CodeEmitter Memory Foot Reduction
...Hi Aaron,
>>
>> I'm sorry for not getting back to you sooner. I work fairly LIFO and the
>> craziness that has happened since your emails have distracted me.
>>
>> One problem with this patch is that (for example) X86TargetMachine.cpp
>> refers to the "createX86ObjectCodeEmitterPass" symbol, which forces the code
>> emitter to object code emitter to be linked into the X86 target module.
>> There is still no way to create a JIT without two copies of the code
>> emitter template. I believe that aligning this work with Daniels work to
>> make the ta...
2009 Jul 16
2
[LLVMdev] [patch] CodeEmitter Memory Foot Reduction
...>>> I'm sorry for not getting back to you sooner. I work fairly LIFO and the
>>> craziness that has happened since your emails have distracted me.
>>>
>>> One problem with this patch is that (for example) X86TargetMachine.cpp
>>> refers to the "createX86ObjectCodeEmitterPass" symbol, which forces the code
>>> emitter to object code emitter to be linked into the X86 target module.
>>> There is still no way to create a JIT without two copies of the code
>>> emitter template. I believe that aligning this work with Daniels work to
>>...
2009 Jul 16
0
[LLVMdev] [patch] CodeEmitter Memory Foot Reduction
...y for not getting back to you sooner. I work fairly LIFO and
> the
> >>> craziness that has happened since your emails have distracted me.
> >>>
> >>> One problem with this patch is that (for example) X86TargetMachine.cpp
> >>> refers to the "createX86ObjectCodeEmitterPass" symbol, which forces the
> code
> >>> emitter to object code emitter to be linked into the X86 target module.
> >>> There is still no way to create a JIT without two copies of the code
> >>> emitter template. I believe that aligning this work with Dani...