From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, anatoly.burakov@intel.com,
vladimir.medvedkin@intel.com, ian.stokes@intel.com,
john.mcnamara@intel.com
Subject: Re: [PATCH] build: remove support for icc compiler
Date: Wed, 5 Feb 2025 08:33:04 -0800 [thread overview]
Message-ID: <20250205083304.7934758e@hermes.local> (raw)
In-Reply-To: <20250205161823.2849595-1-bruce.richardson@intel.com>
On Wed, 5 Feb 2025 16:18:19 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:
> The Intel-produced compiler "icc" has been replaced by the newer
> clang-based "icx" compiler. DPDK compilation has also not been tested
> recently with the icc compiler, so let's remove doc and code references
> to icc, and any special macros or build support that was added for it.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Probably should add a release note for this. But overall looks like a great idea.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2025-02-05 16:33 UTC|newest]
Thread overview: 15+ 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 [this message]
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 ` [PATCH v2 0/2] replace icc support with icx Bruce Richardson
2025-02-05 18:29 ` [PATCH v2 1/2] drivers: fix build warnings when using icx Bruce Richardson
2025-02-10 10:55 ` Stokes, Ian
2025-02-05 18:29 ` [PATCH v2 2/2] build: replace support for icc with icx Bruce Richardson
2025-02-06 15:19 ` David Marchand
2025-02-10 10:55 ` Stokes, Ian
2025-02-10 17:18 ` [PATCH v3] " Bruce Richardson
2025-02-11 9:50 ` David Marchand
2025-02-11 10:08 ` Bruce Richardson
2025-02-11 10:51 ` David Marchand
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=20250205083304.7934758e@hermes.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@intel.com \
--cc=john.mcnamara@intel.com \
--cc=vladimir.medvedkin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.