From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>
Cc: <techboard@dpdk.org>
Subject: Re: [RFC PATCH] build: reduce use of AVX compiler flags
Date: Wed, 26 Mar 2025 16:21:54 +0000 [thread overview]
Message-ID: <Z-QposchDMAmn83I@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250325172215.3360590-1-bruce.richardson@intel.com>
On Tue, Mar 25, 2025 at 05:22:15PM +0000, Bruce Richardson wrote:
> When doing a build for a target that already has the instruction sets
> for AVX2/AVX512 enabled, skip emitting the AVX compiler flags, or the
> skylake-avx512 '-march' flags, as they are unnecessary. Instead, when
> the default flags produce the desired output, just use them unmodified.
>
> Depends-on: series-34915 ("remove component-specific logic for AVX builds")
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>
> This patchset depends on the previous AVX rework. However, sending it
> separately as a new RFC because it effectively increases the minimum
> compiler versions needed for x86 builds - from GCC 5 to 6, and
> Clang 3.6 to 3.9.
>
> For now, I've just documented that as an additional note in the GSG that
> these versions are recommended, but it would be simpler if we could just
> set them as the required minimum baseline (at least in the docs).
>
> Feedback on these compiler version requirements welcome.
>
+techboard
Ping for a little bit of feedback for this. Are we ok to bump the minimum
compiler versions as described above, or will I continue with the approach
in this RFC of keeping the minimum and just recommending the higher
versions for x86 platforms?
For reference GCC 6.1 was released April 2016[1], and, Clang 3.9 was
released Sept 2016[2]
/Bruce
[1] https://gcc.gnu.org/gcc-6/
[2] https://releases.llvm.org/
next prev parent reply other threads:[~2025-03-26 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 17:22 Bruce Richardson
2025-03-26 16:21 ` Bruce Richardson [this message]
2025-03-26 18:06 ` Morten Brørup
2025-03-26 19:20 ` Stephen Hemminger
2025-03-27 7:55 ` DPDK compilers and RHEL 7 support Morten Brørup
2025-03-27 11:11 ` Kevin Traynor
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=Z-QposchDMAmn83I@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=techboard@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).