Displaying 9 results from an estimated 9 matches for "setpoisonmemory".
2013 Oct 01
2
[LLVMdev] JITMemoryManager
...ager *mgr() const = 0;
public:
/*
* From JITMemoryManager
*/
virtual void setMemoryWritable() {
return mgr()->setMemoryWritable();
}
virtual void setMemoryExecutable() {
return mgr()->setMemoryExecutable();
}
virtual void setPoisonMemory(bool poison) {
return mgr()->setPoisonMemory(poison);
}
virtual void AllocateGOT() {
mgr()->AllocateGOT();
/*
* isManagingGOT() is not virtual in base class so we can't delegate.
* Instead we mirror the value of HasGOT in our inst...
2013 Oct 02
0
[LLVMdev] JITMemoryManager
.../*
> * From JITMemoryManager
> */
> virtual void setMemoryWritable() {
> return mgr()->setMemoryWritable();
> }
> virtual void setMemoryExecutable() {
> return mgr()->setMemoryExecutable();
> }
> virtual void setPoisonMemory(bool poison) {
> return mgr()->setPoisonMemory(poison);
> }
> virtual void AllocateGOT() {
> mgr()->AllocateGOT();
> /*
> * isManagingGOT() is not virtual in base class so we can't delegate.
> * Instead we mirror the...
2009 Jul 03
0
[LLVMdev] JIT allocates global data in function body memory
...t either, but it was hard to construct a
unittest that fails properly under release mode without it. It also
seems like it would be a useful feature for writing unit tests for
other custom memory managers. I can either axe it and let the test
only do proper testing in debug mode, or I could add a
setPoisonMemory(bool poison) method to the JITMemoryManager interface.
Which would you prefer?
Reid
2013 Oct 02
3
[LLVMdev] JITMemoryManager
...oryManager
>> */
>> virtual void setMemoryWritable() {
>> return mgr()->setMemoryWritable();
>> }
>> virtual void setMemoryExecutable() {
>> return mgr()->setMemoryExecutable();
>> }
>> virtual void setPoisonMemory(bool poison) {
>> return mgr()->setPoisonMemory(poison);
>> }
>> virtual void AllocateGOT() {
>> mgr()->AllocateGOT();
>> /*
>> * isManagingGOT() is not virtual in base class so we can't delegate.
>>...
2009 Jul 02
2
[LLVMdev] JIT allocates global data in function body memory
The patch looks good to me. But we cannot allow AllocateGVsWithCode to
be initialized to be false yet. Can you add a mechanism to define the
behavior when the JIT is created / initialized?
Also, I am not crazy about this being moved to JITMemoryManager.h.
This seems like implementation detail that should be kept hidden.
+ // If the PoisonMemory parameter is true, freed memory should be
2009 Jul 06
2
[LLVMdev] JIT allocates global data in function body memory
...to construct a
> unittest that fails properly under release mode without it. It also
> seems like it would be a useful feature for writing unit tests for
> other custom memory managers. I can either axe it and let the test
> only do proper testing in debug mode, or I could add a
> setPoisonMemory(bool poison) method to the JITMemoryManager interface.
> Which would you prefer?
My preference would be to add a method to JITMemoryManager.
Thanks,
Evan
>
> Reid
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu...
2012 Sep 24
0
[LLVMdev] [llvm-commits] Fwd: Re: [PATCH] Fix for bug in JIT exception table allocation
...protected:
+ virtual RecordingJITMemoryManager* CreateMemoryManager() {
+ return new RecordingJITMemoryManager;
+ }
+
virtual void SetUp() {
M = new Module("<main>", Context);
- RJMM = new RecordingJITMemoryManager;
+ RJMM = CreateMemoryManager();
RJMM->setPoisonMemory(true);
std::string Error;
+ TargetOptions Options;
+ Options.JITExceptionHandling = true;
TheJIT.reset(EngineBuilder(M).setEngineKind(EngineKind::JIT)
.setJITMemoryManager(RJMM)
- .setErrorStr(&Error).create());
+ .setErrorStr(&a...
2012 Aug 22
1
[LLVMdev] [PATCH] Fix for bug in JIT exception table allocation (no test yet)
On Aug 21, 2012, at 2:12 PM, Michael Muller <mmuller at enduden.com> wrote:
>
> Hi, I found a bug in the code that generates exception tables, I've attached
> what I think is the correct fix.
>
> When you run out of space writing to a buffer, the buffer management code
> simply stops writing at the end of the buffer. It is the responsibility of
> the caller to
2012 Aug 23
0
[LLVMdev] [PATCH] Fix for bug in JIT exception table allocation (no test yet)
Eric Christopher wrote:
>
> On Aug 21, 2012, at 2:12 PM, Michael Muller <mmuller at enduden.com> wrote:
>
> >
> > Hi, I found a bug in the code that generates exception tables, I've attached
> > what I think is the correct fix.
> >
> > When you run out of space writing to a buffer, the buffer management code
> > simply stops writing at the