RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1206133 - atomic_cas32 doesn't work on ppc
Summary: atomic_cas32 doesn't work on ppc
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: boost
Version: 6.7
Hardware: ppc64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jonathan Wakely
QA Contact: Miloš Prchlík
URL:
Whiteboard:
Depends On: 1002578
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-26 12:08 UTC by Miloš Prchlík
Modified: 2015-03-26 14:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1002578
Environment:
Last Closed: 2015-03-26 14:17:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Miloš Prchlík 2015-03-26 12:08:24 UTC 
This issue affects RHEL6.7 builds too (as expected, fixed RHEL7 version is too high for RHEL6.7), is backporting the bug fix an option?

Version-Release number of selected component (if applicable):
boost-1.41.0-27.el6


+++ 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):
boost-devel-1.54.0-2.fc20.ppc

How reproducible:
Always

Steps to Reproduce:
1. Compile and run the attached reproducer

Actual results:
2

Expected results:
0

Additional info:
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.
https://admin.fedoraproject.org/updates/boost-1.53.0-14.fc19

--- 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 ---

Package boost-1.53.0-14.fc19:
* 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:
https://admin.fedoraproject.org/updates/FEDORA-2013-15639/boost-1.53.0-14.fc19
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.
Comment 1 Jonathan Wakely 2015-03-26 14:08:26 UTC 
The code in RHEL 6.7 looks OK.

The upstream bug was introduced to Boost by https://svn.boost.org/trac/boost/changeset/77912 three years ago, long after Boost 1.41 was released.
Comment 2 Miloš Prchlík 2015-03-26 14:17:45 UTC 
Yes, after another investigation of test case' output I found out that test case did fail but for absolutely different reason I didn't correctly interpreted. No bug @ RHEL6.7 spotted then...
Note You need to log in before you can comment on or make changes to this bug.