Re: C++ Memory Management Innovation: GC Allocator

{ Please do not quote extraneous material, such as the clc++m banner.
  Please also note that top posting is discouraged in this group. -mod }

Yes, GC Allocator is not thread-safe. It's my EMPHASES in
implementation section. And that is
why GC Allocator is so fast.

I don't think implementing a producer/consumer pattern is a common
case. So, why not implement an allocator without a multithreaded lock,
then use it with a explicit lock when you implement a producer/
consumer pattern (or something that need to share memory)?

On 4ÔÂ22ÈÕ, ÉÏÎç5ʱ39·Ö, "Chris Thomasson" <cris...@[EMAIL PROTECTED]
> wrote:
> "xu****wei" <xu****we...@[EMAIL PROTECTED]
> wrote in message
>
> AFAICT, your implementation is not thread-safe. For instance, I could
not
> use it to implement a producer/consumer pattern. Thread A allocates
blocks
> and p***** them to thread B which frees them. Am I missing something?

{ banner removed -mod }

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]