DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v2 0/2] replace icc support with icx
Date: Wed,  5 Feb 2025 18:29:13 +0000	[thread overview]
Message-ID: <20250205182918.4041268-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20250205161823.2849595-1-bruce.richardson@intel.com>

The "icc" compiler has been replaced by the newer icx one, so remove
references and workarounds for icc in our codebase. Building with
icx already works, all-be-it with warnings, so we can just fix the
few warnings and report it as supported in our docs in place of icc.

v2:
* include a patch to fix the warnings with icx.

Bruce Richardson (2):
  drivers: fix build warnings when using icx
  build: replace support for icc with icx

 app/test-pmd/testpmd.h                        |  4 ----
 app/test/test_pie.c                           |  5 -----
 app/test/test_red.c                           |  5 -----
 buildtools/check-symbols.sh                   |  6 ++----
 .../contributing/img/patch_cheatsheet.svg     |  2 +-
 doc/guides/linux_gsg/sys_reqs.rst             |  3 +--
 doc/guides/nics/enic.rst                      |  2 +-
 doc/guides/nics/hinic.rst                     |  1 -
 doc/guides/nics/hns3.rst                      |  1 -
 doc/guides/nics/ngbe.rst                      |  1 -
 doc/guides/nics/txgbe.rst                     |  1 -
 doc/guides/prog_guide/lto.rst                 |  2 +-
 .../prog_guide/writing_efficient_code.rst     |  2 +-
 doc/guides/rel_notes/known_issues.rst         | 19 -------------------
 doc/guides/rel_notes/release_25_03.rst        |  5 +++++
 drivers/common/idpf/meson.build               |  3 +++
 drivers/net/ena/ena_ethdev.c                  |  1 -
 drivers/net/intel/i40e/meson.build            |  3 +++
 drivers/net/intel/iavf/meson.build            |  3 +++
 drivers/net/intel/ice/meson.build             |  3 +++
 drivers/net/mlx5/mlx5_rxtx_vec_altivec.h      |  2 +-
 drivers/net/virtio/meson.build                |  2 --
 drivers/net/virtio/virtio_rxtx_packed.h       |  5 -----
 dts/framework/config/__init__.py              |  2 --
 dts/framework/testbed_model/posix_session.py  |  2 --
 lib/eal/common/eal_common_dynmem.c            |  1 -
 lib/eal/include/rte_common.h                  |  6 ++----
 lib/eal/x86/include/rte_rtm.h                 |  2 +-
 lib/eal/x86/include/rte_vect.h                | 15 +--------------
 lib/sched/rte_pie.c                           |  4 ----
 lib/sched/rte_red.c                           |  4 ----
 lib/sched/rte_sched.c                         |  5 -----
 lib/vhost/meson.build                         |  2 --
 lib/vhost/vhost.h                             |  5 -----
 34 files changed, 29 insertions(+), 100 deletions(-)

--
2.43.0


  parent reply	other threads:[~2025-02-05 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 16:18 [PATCH] build: remove support for icc compiler Bruce Richardson
2025-02-05 16:33 ` Stephen Hemminger
2025-02-05 17:03 ` David Marchand
2025-02-05 17:32   ` Bruce Richardson
2025-02-05 17:46     ` Bruce Richardson
2025-02-05 18:29 ` Bruce Richardson [this message]
2025-02-05 18:29   ` [PATCH v2 1/2] drivers: fix build warnings when using icx Bruce Richardson
2025-02-05 18:29   ` [PATCH v2 2/2] build: replace support for icc with icx Bruce Richardson

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=20250205182918.4041268-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.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).