Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1470878[details]
reproducer source file
Description of problem: When using the -On flag compiling with gcc on ppc64 and ppc64le architectures, feeding an int as a parameter to a function expecting a variable of type uint8_t results in different values from x86_64.
Version-Release number of selected component (if applicable):
Reproduced on gcc 4.8.5-16.ppc64le, gcc 4.8.5-28.ppc64le, and gcc 4.8.5-16.ppc64.
How reproducible:
Issue is consistently reproducible.
Steps to Reproduce:
See attached test application.
Actual results:
In the test application, i2 gets truncated (i2 == 176) on all architectures of interest when using either -O0 or -O{1,2,3}.
Expected results:
In the test application, i2 gets truncated (i2 == 176) when using -O0 on all architectures of interest, but when using -O1 or higher, i2 doesn't get truncated (i2 == 432) on ppc64 or ppc64le.
Additional info: Customer reports issue also exists on gcc 6.3, but haven't reproduced it yet.
Created attachment 1470878 [details] reproducer source file Description of problem: When using the -On flag compiling with gcc on ppc64 and ppc64le architectures, feeding an int as a parameter to a function expecting a variable of type uint8_t results in different values from x86_64. Version-Release number of selected component (if applicable): Reproduced on gcc 4.8.5-16.ppc64le, gcc 4.8.5-28.ppc64le, and gcc 4.8.5-16.ppc64. How reproducible: Issue is consistently reproducible. Steps to Reproduce: See attached test application. Actual results: In the test application, i2 gets truncated (i2 == 176) on all architectures of interest when using either -O0 or -O{1,2,3}. Expected results: In the test application, i2 gets truncated (i2 == 176) when using -O0 on all architectures of interest, but when using -O1 or higher, i2 doesn't get truncated (i2 == 432) on ppc64 or ppc64le. Additional info: Customer reports issue also exists on gcc 6.3, but haven't reproduced it yet.