[fpc-devel] volatile variables
andrew.t.brunner at gmail.com
Tue Jun 28 16:38:57 CEST 2011
On Tue, Jun 28, 2011 at 9:33 AM, Michael Schnell <mschnell at lumino.de> wrote:
> And this has been discussed in the other message: If the variable in fact is
> global the compiler needs to avoid caching it, if it is static and the
> function is in another module it might still decide to cache it, but you are
> right: it is not likely that it does make this difference.
Well, I think one issue is that each core has it's own cache.
1.) How can we get the core to not relent and have the code handed off
to another core until we're finished?
2.) How can we get the core to have a synchronised copy of a
particular variable (aside from CAS)?
More information about the fpc-devel