+++ This bug was initially created as a clone of Bug #1002578 +++
Description of problem:
atomic_cas32 doesn't work on ppc
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Compile and run the attached reproducer
This breaks IPC and can cause never-ending loops, etc., for example see bug 1001203.
--- Additional comment from Jaroslav Škarvada on 2013-08-29 15:21:17 CEST ---
It seems like typo in the ASM. The 1.53 seems to be also affected.
--- Additional comment from Jaroslav Škarvada on 2013-08-29 15:27:53 CEST ---
Decreasing the version to f20.
--- Additional comment from Petr Machata on 2013-08-30 00:25:52 CEST ---
Filed upstream as https://svn.boost.org/trac/boost/ticket/9065
I think a better fix is simply swapping the incoming arguments of the inline assembly block, as that way they match the incoming arguments of the function itself. That's what I'll apply in F 19+.
--- Additional comment from Fedora Update System on 2013-09-02 11:34:23 CEST ---
boost-1.53.0-14.fc19 has been submitted as an update for Fedora 19.
--- Additional comment from Petr Machata on 2013-09-02 11:40:02 CEST ---
Note that I have added the fix to F20 and Rawhide as well.
--- Additional comment from Fedora Update System on 2013-09-03 01:25:53 CEST ---
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing boost-1.53.0-14.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
--- Additional comment from Fedora Update System on 2013-09-08 02:35:22 CEST ---
boost-1.53.0-14.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
Currently blocking some epel-7 packages.
Verified for build boost-1.53.0-23.el7.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.