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.

Description of problem:
The testVMX test-suite -- which checks the correctness of Altivec/VMX instructions on POWER6 -- reported some errors on RHEL6 Alpha1 on a P6 system. The same test-suite runs fine on 5.4.

The testVMX suite is available at http://www.bsc.es/plantillaH.php?cat_id=215


Version-Release number of selected component (if applicable):
gcc-4.4.0-4.ppc64
gcc-c++-4.4.0-4.ppc64

How reproducible:
every time

Steps to Reproduce:
1. wget http://www.bsc.es/projects/deepcomputing/pblade/pblade_tuning/testVMX-0.2.2.tar.gz
2. tar xf testVMX-0.2.2.tar.gz; cd testVMX-0.2.2
3. make gcc
4. ./testVMX-gcc-32
5. ./testVMX-gcc-64
6. ./testVMX-g++-32
7. ./testVMX-g++-64

Actual results:
Function vec_cmpgt [type char]            ===> Error
Function vec_cmpgt [type short]           ===> Error
Function vec_cmpgt [type unsigned int]    ===> Error
Function vec_cmplt [type char]            ===> Error
Function vec_cmplt [type short]           ===> Error
Function vec_cmplt [type unsigned short]  ===> Error
Function vec_cmplt [type unsigned int]    ===> Error

Expected results:
no errors

Additional info:
Due to bug 511304 and bug 511908, you may need to install RHEL 6 from DVD (not a network install) on a non-blade system to reproduce.

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Out of curiousity, if you put the test suite in a package, and build it in a build env/mock root, does that fail too?

It fails even on Fedora 11 on G5.
Fixed thusly:
http://gcc.gnu.org/ml/gcc-patches/2009-09/msg01479.html
waiting for upstream approval.

For QA, it would be nice to put this testVMX testsuite into RHTS and grep for ===> Error lines.

Fixed in gcc-4.4.1-16.

Fixed in 'gcc-4.4.1-16'. 'gcc-4.4.1-22.el6' included in compose 'RHEL6.0-20091028.0'.
Moving to ON_QA.

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.