[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 12:07:38 +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 #7, bug #33392 (project gnustep):

Yes. :-)

It may be slightly more complicated but we'll need to address 
the complication. :-(

I think we'd like gnustep-make to generally add -march=xxx 
(where "xxx" is something more recent than i386, a CPU released 
24 years ago) but make it configurable when you configure 

I'd expect the default, for a i686 machine, would be 
-march=i686.  As the Pentium Pro was introduced in 1995, code 
built using -march=i686 should run on all ix86 CPUs produced in 
the last 16 years or so, which should probably be safe enough as 
a default ?

And, if you're building for your own machine, you could use -march=native to
get max performance.

Presumably gnustep-base's configure would then need to do the 
check that Niels was mentioning, but also taking into account the -march=xxx
flag added by gnustep-make.

Does it make sense as a plan ?



Reply to this item at:


  Message sent via/by Savannah

reply via email to

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