From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1251] PPC64le: 23.07 RC1 build failed for power10 on RHEL 9.0
Date: Mon, 26 Jun 2023 16:54:15 +0000 [thread overview]
Message-ID: <bug-1251-3-bKsSR0vx4O@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1251-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1251
David Christensen (drc@linux.vnet.ibm.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from David Christensen (drc@linux.vnet.ibm.com) ---
GCC bugzilla has been opened:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110411 to track the issue.
Suggested workaround is to enable "-mno-block-ops-vector-pair" for gcc < 11.4
when building for power10 architecture. (GCC 11.4 enables this option by
default when -mcpu=power10.)
Proposed fix:
diff --git a/config/ppc/meson.build b/config/ppc/meson.build
index 1cba44011f..160b203cb1 100644
--- a/config/ppc/meson.build
+++ b/config/ppc/meson.build
@@ -105,6 +105,14 @@ else
endif
endif
machine_args = ['-mcpu=' + cpu_instruction_set, '-mtune=' +
cpu_instruction_set]
+
+# gcc versions < 11.4 may fail to build for power10, see
https://bugs.dpdk.org/show_bug.cgi?id=1251.
+# Explicitly specify a default used in gcc 11.4 and later to workaround the
issue
+if (cpu_instruction_set == 'power10' and cc.get_id() == 'gcc' and
+ cc.version().version_compare('<=11.4'))
+ machine_args += '-mno-block-ops-vector-pair'
+endif
+
dpdk_conf.set('RTE_MACHINE', cpu_instruction_set)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3838 bytes --]
prev parent reply other threads:[~2023-06-26 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 21:42 bugzilla
2023-06-26 16:54 ` bugzilla [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1251-3-bKsSR0vx4O@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).