Re: [Boost-bugs] [Boost C++ Libraries] #9426: boost::atomic gcc-cas related specializations patch

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #9426: boost::atomic gcc-cas related specializations patch
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-11-24 00:29:31

#9426: boost::atomic gcc-cas related specializations patch
-------------------------------------+--------------------------
  Reporter:  Piotr Kobzda <pikob@…>  |      Owner:  timblechmann
      Type:  Patches                 |     Status:  new
 Milestone:  To Be Determined        |  Component:  atomic
   Version:  Boost 1.55.0            |   Severity:  Problem
Resolution:                          |   Keywords:
-------------------------------------+--------------------------

Comment (by Piotr Kobzda <pikob@…>):

 > not being familiar with mipsel toolchains, i wonder: what (gcc)
 compilers are commonly used for this architecture?

 Hard to tell precisely, since it depends on strategy of the processor
 vendors adopted to theirs individual customers (which, in general, I'm not
 too aware of).  But I'm afraid, that some people can still use toolchains
 for Mips older than 4.1 (which I think is initial version supporting
 `__sync_synchronize` builtin).
 Nevertheless, I agree that having just gcc version check would most likely
 be enough here -- anyone interested in using of older toolchains will
 still safely use default alternative.

 I'm just not sure, whether suggested use of `__GCC_HAVE_SYNC_*` macros
 shall be preferred before simple gcc version check -- official
 documentation for gcc 4.1 does not list it in predefined macros list, thus
 I'd rather prefer use of version check.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/9426#comment:9>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.