shared methods
Johannes Pfau
nospam at example.com
Sat Jan 25 15:20:14 PST 2014
Am Sat, 25 Jan 2014 21:48:39 +0000
schrieb "Kagamin" <spam at here.lot>:
> Also if you read a shared value with atomicLoad every time, this
> disallows caching in registers or on stack, which is also
> performance hit. The shared value should be read once and cached
> if possible.
Yes, I came to the same conclusion. If we combine volatile
and shared into one qualifier we'll always have a certain performance
hit.
Great, now we have to convince Walter that we have to undeprecate
volatile for embedded programming...
More information about the Digitalmars-d-learn
mailing list