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 883748 - The stack feature from libatomic_ops does not work properly on ppc/ppc64
Summary: The stack feature from libatomic_ops does not work properly on ppc/ppc64
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gc
Version: 6.4
Hardware: powerpc
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Raiskup
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On: 1096574
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-05 08:22 UTC by Pavel Raiskup
Modified: 2017-08-16 06:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-16 06:44:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Raiskup 2012-12-05 08:22:35 UTC
Hello, we still have problems with AO_stack* feature on ppc/ppc64.  The
testsuite for AO_stack* calls fails on 'test_stack' application.  As these
atomic operations are low-level and hard to make portable, this behaviour is
quite expected in early phases.

Upstream has been working on this problem recently:

  http://article.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/5238/match=test_stack

But the solution does not help us 100%.

I have tried to find some workaround/fix, but unsuccessful yet.  I have also
contacted upstream for help and I'll work on this in future.  But now I tend to
at least document *now* that this feature does not work properly in RHEL.

I have tried test on several PowerPCs, and I know only that it does not work on
all ppcs (on some of them testsuite passes).

Pavel

Comment 3 Pavel Raiskup 2012-12-18 14:02:04 UTC
I've found nasty workaround, proposed upstream .. but it needs more
investigation.

http://news.gmane.org/find-root.php?group=gmane.comp.programming.garbage-collection.boehmgc&article=5486

Pavel

Comment 4 RHEL Program Management 2013-10-14 00:11:45 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 7 Pavel Raiskup 2017-08-16 06:44:00 UTC
It is too late for RHEL6 so I'm closing this bug. Seems like the latest
fedora package builds libatomic_ops correctly on all architectures, and
the test passes -- no need to track this more downstream.


Note You need to log in before you can comment on or make changes to this bug.