From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
Vipin Varghese <vipin.varghese@amd.com>
Subject: Re: [PATCH v2] build/x86: fix support for older compilers
Date: Thu, 3 Jul 2025 09:10:09 -0700 [thread overview]
Message-ID: <20250703091009.7ed2166b@hermes.local> (raw)
In-Reply-To: <CAJFAV8zxhi8DmhxKFrPnFwFJ60z-eMSH3x=32gKzEAu8xJW6tQ@mail.gmail.com>
On Thu, 3 Jul 2025 10:12:10 +0200
David Marchand <david.marchand@redhat.com> wrote:
> On Thu, Jul 3, 2025 at 10:01 AM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > On Wed, Jul 02, 2025 at 11:22:42AM -0700, Stephen Hemminger wrote:
> > > On Wed, 2 Jul 2025 17:00:45 +0100
> > > Bruce Richardson <bruce.richardson@intel.com> wrote:
> > >
> > > > Some older compilers e.g. gcc 8.5, do not support overriding
> > > > -march=native with another architecture, leading to build warnings such
> > > > as reported in Bugzilla (link below). Add a check for that case, and
> > > > explicitly add the avx512 flags if necessary.
> > > >
> > > > Note: it appears that it is only the "native" flag that isn't
> > > > overridden, which makes the issue hard to reproduce e.g. using
> > > > godbolt.org, or on a modern machine. For example, testing with gcc 8.5
> > > > on a haswell machine, using 'native' vs explicit 'haswell':
> > > >
> > > > gcc -march=native -march=skylake-avx512 -dM -E - < /dev/null | grep AVX512 | wc -l
> > > > 0
> > > >
> > > > gcc -march=haswell -march=skylake-avx512 -dM -E - < /dev/null | grep AVX512 | wc -l
> > > > 5
> > > >
> > > > Bugzilla ID: 1736
> > > > Fixes: e361ae3f59d3 ("build: reduce use of AVX compiler flags")
> > > >
> > > > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > > > ---
> > > > config/x86/meson.build | 7 ++++++-
> > > > 1 file changed, 6 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/config/x86/meson.build b/config/x86/meson.build
> > > > index e2ccfb6d12..0dcc5ddee4 100644
> > > > --- a/config/x86/meson.build
> > > > +++ b/config/x86/meson.build
> > > > @@ -71,8 +71,13 @@ avx512_march_flag = '-march=x86-64-v4'
> > > > if not cc.has_argument(avx512_march_flag)
> > > > avx512_march_flag = '-march=skylake-avx512'
> > > > endif
> > > > +# workaround for older compilers, e.g. gcc 8.5 on RHEL 8.
> > > > +# if march flag overriding doesn't work, explicitly add flags for AVX512.
> > > > +if cc.get_define('__AVX512F__', args: [machine_args, avx512_march_flag]) == ''
> > > > + avx512_march_flag = ['-mavx512f', '-mavx512bw', '-mavx512cd', '-mavx512dq', '-mavx512vl']
> > > > +endif
> > >
> > > RHEL 8.5 reached end of extended support cycle (EOL).
> > > Why are we still supporting it?
> >
> > Folks working for Redhat can answer better than me, but according to [1]
> > it's not EOL yet. Also, we support it in DPDK because users are still using
>
> RHEL 8 is not EOL.
>
>
Right but 8.5 is, did compiler get fixed in later 8.X versions?
next prev parent reply other threads:[~2025-07-03 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 15:51 [PATCH] " Bruce Richardson
2025-07-02 15:53 ` Bruce Richardson
2025-07-02 16:00 ` [PATCH v2] " Bruce Richardson
2025-07-02 18:22 ` Stephen Hemminger
2025-07-03 8:00 ` Bruce Richardson
2025-07-03 8:12 ` David Marchand
2025-07-03 16:10 ` Stephen Hemminger [this message]
2025-07-03 10:21 ` [PATCH v3] " Bruce Richardson
2025-07-03 13:23 ` Thomas Monjalon
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=20250703091009.7ed2166b@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=vipin.varghese@amd.com \
/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).