Re: [dev] Executable Memory

Stephan Bergmann wrote: Matthias Huetsch wrote: Hi Stephan, sorry for jumping in late; see my comments inline... Stephan Bergmann wrote On 03/17/06 15:59,: [...] Part of my motivation is the issue that you mentioned in the email that started this thread, i.e. issue 47132 (and its predeces

Re: [dev] Executable Memory

Matthias Huetsch wrote: Hi Stephan, sorry for jumping in late; see my comments inline... Stephan Bergmann wrote On 03/17/06 15:59,: [...] Part of my motivation is the issue that you mentioned in the email that started this thread, i.e. issue 47132 (and its predecessor issue 25250, that has b

Re: [dev] Executable Memory

Hi Stephan, sorry for jumping in late; see my comments inline... Stephan Bergmann wrote On 03/17/06 15:59,: Kay Ramme - Sun Germany - Hamburg wrote: Stephan, Stephan Bergmann wrote: 2 Add rtl_allocateExecutableMemory to rtl/alloc.h, which internally uses the same logic as rtl_allocateMemo

Re: [dev] Executable Memory

On Fri, 2006-03-17 at 10:17 +0100, Stephan Bergmann wrote: > 3 Exploiting the fact that the executable memory in question is never > freed, add a simple, special-purpose (executable) memory allocator to > bridges/source/cpp_uno/shared. It would work similar to > rtl_allocateMemory by using mm

Re: [dev] Executable Memory

Kay Ramme - Sun Germany - Hamburg wrote: Stephan, Stephan Bergmann wrote: 2 Add rtl_allocateExecutableMemory to rtl/alloc.h, which internally uses the same logic as rtl_allocateMemory, but works on a second set of memory, independent of the original set of memory managed by plain rtl_allo

Re: [dev] Executable Memory

Stephan, Stephan Bergmann wrote: 2 Add rtl_allocateExecutableMemory to rtl/alloc.h, which internally uses the same logic as rtl_allocateMemory, but works on a second set of memory, independent of the original set of memory managed by plain rtl_allocateMemory (and the second set of memory wo

[dev] Executable Memory

Hi all, In the C++ UNO bridges, we need executable memory for the genereated vtables, see . (Strictly speaking, it is not the memory for the vtables themselves that needs to be executable, but rather the memory for the generated code thu