This is the mail archive of the gcc-patches@gcc.gnu.org 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]

Re: [cxx-mem-model] compare_exchange implementation


On 10/19/2011 11:31 AM, Andrew MacLeod wrote:
> If, which is more likely as I think about it, thats not the case and
> the fences can look like they do in the second example (closer to the
> CAS than the copies) , then the CAS can take care of both fences,
> which would be much more preferable and clean..

Indeed.

>>> So if the CAS can handle it all, why does it matter if the pattern
>>> has a single "compressed" parameter for the 3 values, or whether it
>>> simply explicitly lists all three?
>> *shrug* Just for less memory consumption.  It *could* remain 3 values.
>>
> Does it really make a measurable memory difference?  I can certainly jam them together...

Eh, you're right, probably not a measurable difference.


r~


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