[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #33392] Multi-thread bug in NSObject retain and release

From: Nicola Pero
Subject: [bug #33392] Multi-thread bug in NSObject retain and release
Date: Thu, 26 May 2011 09:38:09 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20110429 CentOS/3.6-1.el5.centos Firefox/3.6.17

Follow-up Comment #4, bug #33392 (project gnustep):

IIRC, if GCC is compiling for a general x86 machine, it will 
generate code that can run on any i386 processor even produced; 
hence it won't use CPU operations available only in newer CPUs.  
So atomic builtins will become calls to custom functions (and 
could be even slower than a pthread lock).

To use atomic builtins, you need to tell GCC that the CPU is more 
than just a generic ix86 by using -march=pentium or something like 
that.  I'm not sure of the exact -march= or -mtune= option that we 
want to use; we need to look up the options and study them.

The extreme option would be to use -march=native, which would 
provide fast code, but most likely not portable.



Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]