[Bug c++/21251] Placement into shared memory

["mronell at alumni dot upenn dot edu" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From mronell at alumni dot upenn dot edu  2005-04-28 01:32 -------
"Plain Old Data" unfortunately is not a good solution in my case.  I maintain
http://allocator.sourceforge.net which provides an open-source shared memory
allocator for the C++ Standard Template Library.  This allocator has worked
with earlier versions of gcc/g++, but it depends on being able to instantiate
objects successfully in shared memory allowing multiple processes to access
the same objects.  Localized vtable pointers would cause problems.

I have a new version of the allocator revised based on Knuth's Dynamic Memory
Storage algorithm from his Vol. 1.  Its similar to Doug Lea's malloc.

However, as before, my approach depends on being able to place and share C++
objects through shared memory.  Its that still possible? 

Am I missing some esoteric compiler flags?  Is this a bug or future feature request?

Thanks for your suggestions and input.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21251