Subject: Re: [boost] Cache flushing in the constructors
From: Sid Sacek (ssacek_at_[hidden])
Date: 2010-08-04 12:01:40
> Normally, however, an object isn't created by one thread and handed off to
> another, so fences are rarely warranted in a constructor.
> Rob Stewart
Right.
I'm starting to believe the answer to my question is that it is not the responsibility of constructors to solve potential cache-coherency issues, but rather, the code that uses the boost classes must be knowledgeable of the hardware's limitations and make special provisions for it.
Thanks,
-Sid