--- Comment #14 from mronell at alumni dot upenn dot edu 2006-05-03 02:39
---
It seems to me an approach using thunks, or pass by name, or a similar
approach should work. Each process can evaluate the object in shared
memory with reference to the local virtual table to gain access to
--- Comment #11 from mronell at alumni dot upenn dot edu 2005-11-16 02:01
---
If placement using new into shared memory allows process independent memory
referencing, other software tools (including allocators) can be developed.
This request asks, can placement into shared memory
?
--
Summary: Placement into shared memory
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mronell at alumni dot
--
What|Removed |Added
GCC build triplet||i686-pc-linux-gnu
GCC host triplet||i686-pc-linux-gnu
GCC target triplet|
--- Additional Comments From mronell at alumni dot upenn dot edu
2005-04-27 14:56 ---
I believe that the pointer points to a component within the vtable,
but I do not want to jump to that conclusion. When the object is
instantiated in shared memory, the first element seems to be a
--- 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++ Standar
--- Additional Comments From mronell at alumni dot upenn dot edu
2005-05-02 16:49 ---
Apologies for my persistence, but the following is still not clear to
me. Given the last reply to this concern, I now understand:
1. Placement into shared memory is not possible. If processes
