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.
Description of problem:
There is a bug in binutils 2.30 and 2.31 that makes assembler to generate
incorrect AVX512 instructions:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90028
DPDK and Open vSwitch projects automatically checks for a broken functionality
and completely disables support for AVX512 in case of broken binutils.
This means that it's not possible to build DPDK or Open vSwith on rhel8 with
AVX512 support even with '-march=native'. Other projects that doesn't have
build time checks might experience crashes due to incorrect instructions.
Fix exists in upstream and needs to be backported:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=4e518864c879be2e6af4c64415e8775d9a20deaf
Version-Release number of selected component (if applicable):
binutils-2.30-73.el8
Steps to Reproduce:
1. echo 'vpgatherqq 0x8(,%ymm1,1),%ymm0{%k2}' | as --64 -
2. objdump -d --no-show-raw-insn a.out | grep vpgatherqq
Actual results:
0: vpgatherqq 0x1(,%ymm1,1),%ymm0{%k2}
Expected results:
0: vpgatherqq 0x8(,%ymm1,1),%ymm0{%k2}
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 (Low: binutils security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4465