This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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

------- Additional Comments From pinskia at gcc dot gnu dot org  2005-04-28 01:44 -------
(In reply to comment #4)
> 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?

No it is not possible.  Now if you convince the standards committe that this is really should be possible, 
then we will implement their recommendation but as of now, there is no way sorry.

>  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.

What versions?  I really doubt that it worked at all as vtable implementation has only changed on what 
is the layout of the vtable.

> "Plain Old Data" unfortunately is not a good solution in my case.  I maintain
> which provides an open-source shared memory
> allocator for the C++ Standard Template Library.

Hmm, there allocators have specific requirements in C++. 

           What    |Removed                     |Added
             Status|UNCONFIRMED                 |RESOLVED
          Component|c++                         |libstdc++
         Resolution|                            |INVALID
            Version|unknown                     |3.4.3

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]