Displaying 11 results from an estimated 11 matches for "emitjumptableinfo".
2013 Aug 09
1
[LLVMdev] Always put jump tables in code section?
Jump tables (e.g. for dispatching in switch statements) currently
get emitted to a readonly data section, unless -fPIC is in effect
in which case they're emitted into the function's code section.
The code to figure this out (in AsmPrinter::EmitJumpTableInfo())
is not obvious, although commented, and has a FIXME for yet another
special case.
There is clear value to co-locating jump tables with the function
body for -fPIC. I am not so clear on the value of putting them
in a readonly data section in the non-PIC case. Would it be a
problem if they were...
2008 Mar 30
3
[LLVMdev] Being able to know the jitted code-size before emitting
Hi everyone,
vmkit requires to know the size of a jitted method before emitting the
method. This allows to allocate the correct size for the method. The
attached patch creates this functionality when the flag SizedMemoryCode
is on.
In order to implement this functionality, i had to virtualize some
MachineCodeEmitter functions.
Is it OK to commit the patch?
Thanks,
Nicolas
--------------
2008 Apr 01
2
[LLVMdev] Being able to know the jitted code-size before emitting
...unction &F);
>> virtual bool finishFunction(MachineFunction &F);
>>
>> + void initConstantPool(MachineConstantPool *MCP);
>> void emitConstantPool(MachineConstantPool *MCP);
>> void initJumpTableInfo(MachineJumpTableInfo *MJTI);
>> void emitJumpTableInfo(MachineJumpTableInfo *MJTI);
>> @@ -469,19 +476,47 @@
>>
>>
>> void JITEmitter::startFunction(MachineFunction &F) {
>> - uintptr_t ActualSize;
>> - BufferBegin = CurBufferPtr = MemMgr-
>>
>>> startFunctionBody(F.getFunction(),
>>&...
2008 Mar 31
0
[LLVMdev] Being able to know the jitted code-size before emitting
...d startFunction(MachineFunction &F);
> virtual bool finishFunction(MachineFunction &F);
>
> + void initConstantPool(MachineConstantPool *MCP);
> void emitConstantPool(MachineConstantPool *MCP);
> void initJumpTableInfo(MachineJumpTableInfo *MJTI);
> void emitJumpTableInfo(MachineJumpTableInfo *MJTI);
> @@ -469,19 +476,47 @@
>
>
> void JITEmitter::startFunction(MachineFunction &F) {
> - uintptr_t ActualSize;
> - BufferBegin = CurBufferPtr = MemMgr-
> >startFunctionBody(F.getFunction(),
> -...
2008 Apr 01
0
[LLVMdev] Being able to know the jitted code-size before emitting
...;>> virtual bool finishFunction(MachineFunction &F);
>>>
>>> + void initConstantPool(MachineConstantPool *MCP);
>>> void emitConstantPool(MachineConstantPool *MCP);
>>> void initJumpTableInfo(MachineJumpTableInfo *MJTI);
>>> void emitJumpTableInfo(MachineJumpTableInfo *MJTI);
>>> @@ -469,19 +476,47 @@
>>>
>>>
>>> void JITEmitter::startFunction(MachineFunction &F) {
>>> - uintptr_t ActualSize;
>>> - BufferBegin = CurBufferPtr = MemMgr-
>>>
>>>> startFunctionBody(...
2008 Apr 04
3
[LLVMdev] Being able to know the jitted code-size before emitting
...bool finishFunction(MachineFunction &F);
>>>>
>>>> + void initConstantPool(MachineConstantPool *MCP);
>>>> void emitConstantPool(MachineConstantPool *MCP);
>>>> void initJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>> void emitJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>> @@ -469,19 +476,47 @@
>>>>
>>>>
>>>> void JITEmitter::startFunction(MachineFunction &F) {
>>>> - uintptr_t ActualSize;
>>>> - BufferBegin = CurBufferPtr = MemMgr-
>>>>
>>...
2008 Apr 05
2
[LLVMdev] Being able to know the jitted code-size before emitting
...&F);
>>>>>>
>>>>>> + void initConstantPool(MachineConstantPool *MCP);
>>>>>> void emitConstantPool(MachineConstantPool *MCP);
>>>>>> void initJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>>> void emitJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>>> @@ -469,19 +476,47 @@
>>>>>>
>>>>>>
>>>>>> void JITEmitter::startFunction(MachineFunction &F) {
>>>>>> - uintptr_t ActualSize;
>>>>>> - BufferBegin =...
2008 Apr 05
0
[LLVMdev] Being able to know the jitted code-size before emitting
...>>>>>
>>>>>>> + void initConstantPool(MachineConstantPool *MCP);
>>>>>>> void emitConstantPool(MachineConstantPool *MCP);
>>>>>>> void initJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>>>> void emitJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>>>> @@ -469,19 +476,47 @@
>>>>>>>
>>>>>>>
>>>>>>> void JITEmitter::startFunction(MachineFunction &F) {
>>>>>>> - uintptr_t ActualSize;
>>>>>&...
2008 Apr 04
0
[LLVMdev] Being able to know the jitted code-size before emitting
...ion(MachineFunction &F);
>>>>>
>>>>> + void initConstantPool(MachineConstantPool *MCP);
>>>>> void emitConstantPool(MachineConstantPool *MCP);
>>>>> void initJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>> void emitJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>> @@ -469,19 +476,47 @@
>>>>>
>>>>>
>>>>> void JITEmitter::startFunction(MachineFunction &F) {
>>>>> - uintptr_t ActualSize;
>>>>> - BufferBegin = CurBufferPtr = MemMgr-...
2008 Apr 07
2
[LLVMdev] Being able to know the jitted code-size before emitting
...>
>>>>>>>> + void initConstantPool(MachineConstantPool *MCP);
>>>>>>>> void emitConstantPool(MachineConstantPool *MCP);
>>>>>>>> void initJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>>>>> void emitJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>>>>> @@ -469,19 +476,47 @@
>>>>>>>>
>>>>>>>>
>>>>>>>> void JITEmitter::startFunction(MachineFunction &F) {
>>>>>>>> - uintptr_t ActualSize;
&...
2008 Apr 07
0
[LLVMdev] Being able to know the jitted code-size before emitting
...>>>>>>> + void initConstantPool(MachineConstantPool *MCP);
>>>>>>>>> void emitConstantPool(MachineConstantPool *MCP);
>>>>>>>>> void initJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>>>>>> void emitJumpTableInfo(MachineJumpTableInfo *MJTI);
>>>>>>>>> @@ -469,19 +476,47 @@
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> void JITEmitter::startFunction(MachineFunction &F) {
>>>>>>>>> - uin...