Michael Schnell schrieb: > On 06/24/2010 10:02 AM, Florian Klaempfl wrote: >> Well, yes, you shouldn't simply use locked operations in a single cpu >> environment, your application should provide different algorithms for >> single and multi cpu/threaded environments if the application really >> contains speed critical code requiring locking. > Do you suggest the application programmer should take care about if the > application runs on a multi.CPU system or a single CPU system ?
Yes. If it's real time or performance critical then he should really know when locking is needed etc. >> This is why FPC uses >> inclocked/declocked for fast reference counting. >> > I don't understand. > > with ARM inclocked() calls InterlocktIncrement, that triggers exactly > this problem. ... because nobody provided a better implementation yet, e.g. i386 does. Nobody provided either code yet which makes dynamic use of strex/ldex as newer arms provide as I did e.g. for move using pld if available because I needed it. _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/mailman/listinfo/fpc-devel
