Displaying 5 results from an estimated 5 matches for "allocateseparategvmemory".
2009 Jun 30
2
[LLVMdev] JIT allocates global data in function body memory
...en sending it to another to
> be executed, and references from one buffer to another won't work in
> that environment. So that model needs to continue to work. If you
> want to generalize it so other models work as well, go ahead.
Maybe what I should do then is change
TargetJITInfo::allocateSeparateGVMemory to allocateGVsWithCode and
invert the meaning, since I feel like most users probably just want
malloc or something similar. You could then subclass the appropriate
TJI class and override that method. Would that be a reasonable API
change? No one else calls or overrides that method. In order to...
2009 Jul 01
0
[LLVMdev] JIT allocates global data in function body memory
...o
>> be executed, and references from one buffer to another won't work in
>> that environment. So that model needs to continue to work. If you
>> want to generalize it so other models work as well, go ahead.
>
> Maybe what I should do then is change
> TargetJITInfo::allocateSeparateGVMemory to allocateGVsWithCode and
> invert the meaning, since I feel like most users probably just want
> malloc or something similar. You could then subclass the appropriate
> TJI class and override that method. Would that be a reasonable API
> change? No one else calls or overrides that m...
2009 Jun 30
0
[LLVMdev] JIT allocates global data in function body memory
On Jun 29, 2009, at 5:41 PMPDT, Reid Kleckner wrote:
> So I (think I) found a bug in the JIT:
> http://llvm.org/bugs/show_bug.cgi?id=4483
>
> Basically, globals used by a function are allocated in the same buffer
> as the first code that uses it. However, when you free the machine
> code, you also free the memory holding the global's data. The address
> is still in the
2009 Dec 25
1
[LLVMdev] JIT buffer code skipping 8 bytes?
On OS X (10.6.2) running on an Intel Core 2 duo with LLVM 2.7 pulled about a month ago from CVS and built in debug mode:
Using the JIT system with exception handling, I am having issues with type infos. "Finally" code (llvm.eh.selector intrinsic call with 0)
works fine (correct landing pads found), as does this call with one type info. My type infos are each 64 bit array GlobalVariables
2009 Jun 30
3
[LLVMdev] JIT allocates global data in function body memory
So I (think I) found a bug in the JIT:
http://llvm.org/bugs/show_bug.cgi?id=4483
Basically, globals used by a function are allocated in the same buffer
as the first code that uses it. However, when you free the machine
code, you also free the memory holding the global's data. The address
is still in the GlobalValue map, so any other code using that global
will access freed memory, which