search for: memoryblock

...of the block. This patch fixes this, and checks that both read and write flags are set. unittests/Support/MemoryTest.cpp (line 101) TEST_P(MappedMemoryTest, BasicWrite) { // This test applies only to writeable combinations if (Flags && !(Flags & Memory::MF_WRITE)) return; MemoryBlock M1 = Memory::allocateMappedMemory(sizeof(int), 0, Flags, EC); ... int *a = (int*)M1.base(); *a = 1; EXPECT_EQ(1, *a); // This line segfaults. ... } -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/2012...

...soundPresets.txt CreateCast Effects path = <CP>\Settings\effects.txt CreateCast Particle Presets path = <CP>\Settings\particle_presets.txt CreateCast Player path = <CP>\Settings\player.txt CreateCast Menu path = *********** SoundEngine::Init() *********** SoundEngine::Init with memoryBlock, size: 46080.000000 kb Created EventSystem Note: I am using Ubuntu 10.04, I did not restarted the system, installed or removed anything . [/code]

The new method Memory::ReleaseRWX has the wrong signature on these two platforms. The argument type is Memory& when it should be MemoryBlock&.

...of the block. This patch fixes this, and checks that both read and write flags are set. unittests/Support/MemoryTest.cpp (line 101) TEST_P(MappedMemoryTest, BasicWrite) { // This test applies only to writeable combinations if (Flags && !(Flags & Memory::MF_WRITE)) return; MemoryBlock M1 = Memory::allocateMappedMemory(sizeof(int), 0, Flags, EC); ... int *a = (int*)M1.base(); *a = 1; EXPECT_EQ(1, *a); // This line segfaults. ... } -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/2012...

...ger : to give it to the object writer (for memory claiming) - MCJITObjectWriter - knows : - the MCJIT : for mapping GlobalVariable <-> native address - the MemoryManager : for claiming memory - mem_raw_ostream - The ostream interface to write data in memory - Currently using a MemoryBlock but will probably be changed for matching JITMemoryManager structure Another point of interest is how the current mappings are implemented in the ExecutionEngine. When applying fixups in the ObjectWriter, we get a symbol name from a MCSymbol. With the current mappings the Writer is forced to kno...

I've just wasted a day chasing my tail because of subtleties introduced to handle the optionality of the DataLayout. I would like to never do this again. =] We now have this attached to the Module with just a flimsy faked-up pass to keep APIs consistent. So, is there any problem with beginning down the path of: 1) Synthesizing a "default" boring DataLayout for all modules that

...x: lib/ExecutionEngine/JIT/JITMemoryManager.cpp > =================================================================== > --- lib/ExecutionEngine/JIT/JITMemoryManager.cpp (revision 46612) > +++ lib/ExecutionEngine/JIT/JITMemoryManager.cpp (working copy) > @@ -256,6 +256,7 @@ > sys::MemoryBlock getNewMemoryBlock(unsigned size); > > std::map<const Function*, MemoryRangeHeader*> FunctionBlocks; > + std::map<const Function*, MemoryRangeHeader*> TableBlocks; > public: > DefaultJITMemoryManager(); > ~DefaultJITMemoryManager(); > @@ -290,6 +291,...

Dear all, Here's a new patch with Evan's comments (thx Evan!) and some cleanups. Now the (duplicated) exception handling code is in a new file: lib/ExecutionEngine/JIT/JITDwarfEmitter. This patch should work on linux/x86 and linux/ppc (tested). Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-exceptions.patch URL: