http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21251
Jackie Rosen jackie.rosen at hushmail dot com changed:
What|Removed |Added
CC|
--- 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 #15 from pinskia at gcc dot gnu dot org 2006-05-03 04:03
---
(In reply to comment #14)
I would like to see if Stroustrup could suggest a better solution? Have
you tried contacting some of that caliber in compiler design for
suggestions?
Why don't you write to
--- Comment #13 from pinskia at gcc dot gnu dot org 2006-04-22 20:44
---
There is no way non PODs will ever work with shared memory. This is why they
are called non-PODs and they never should be shared outside of the program. In
fact non-PODs cannot be passed via var-args or even
--- 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
--- Comment #12 from pinskia at gcc dot gnu dot org 2005-11-16 02:07
---
This almost need to go to the standards committee for how to deal with this
(and maybe instead the IA64 ABI mailing list as we just follow that ABI for
C++).
--
pinskia at gcc dot gnu dot org changed:
--
What|Removed |Added
GCC build triplet||i686-pc-linux-gnu
GCC host triplet||i686-pc-linux-gnu
GCC target triplet|
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-27
14:03 ---
Are you talking about the vtable being at two different locations, well there
is no way since the struct is
a non-POD which means it cannot do many things with.
If you want to share data, try with a POD
--- 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 pcarlini at suse dot de 2005-04-27 15:01
---
(POD (Plain Old Data) is a technical term, defined in the standard, basically
something you can copy bit by bit, via memcpy)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21251
--- 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.
11 matches
Mail list logo
