DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Varghese, Vipin" <Vipin.Varghese@amd.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>,
	"Morten Brørup" <mb@smartsharesystems.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"techboard@dpdk.org" <techboard@dpdk.org>
Subject: RE: [RFC PATCH] build: reduce use of AVX compiler flags
Date: Wed, 9 Apr 2025 09:53:47 +0000	[thread overview]
Message-ID: <PH7PR12MB859614316DC742F0C8A12B3082B42@PH7PR12MB8596.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250326122036.6cc7c02e@hermes.local>

[Public]

Snipped

> > > > 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>

Hi Bruce,

From AMD end we have tested with gcc 12, and 13.
We tried cross checking with and without patch for libraries such as `librte_net_ice and librte_net_i40e`.

We did not find much changes in the assembly code generated.
I hope this is expected? Can you please share any pointers?\

> > > > ---
> > > >
> > > > 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


  parent reply	other threads:[~2025-04-09  9:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 17:22 Bruce Richardson
2025-03-26 16:21 ` Bruce Richardson
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
2025-04-09  9:53       ` Varghese, Vipin [this message]
2025-04-09 11:31         ` [RFC PATCH] build: reduce use of AVX compiler flags Bruce Richardson
2025-04-10  3:49           ` Varghese, Vipin

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=PH7PR12MB859614316DC742F0C8A12B3082B42@PH7PR12MB8596.namprd12.prod.outlook.com \
    --to=vipin.varghese@amd.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=stephen@networkplumber.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).