DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: techboard@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 1/1] doc: add deprecation notice for CPU build flags
Date: Wed,  5 Aug 2020 15:21:41 +0100	[thread overview]
Message-ID: <20200805142141.32337-2-bruce.richardson@intel.com> (raw)
In-Reply-To: <20200805142141.32337-1-bruce.richardson@intel.com>

The RTE_MACHINE_CPUFLAGS_* macros in DPDK build just duplicate info from
the compiler macros, so we can remove them and just use the compiler
versions directly.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
 doc/guides/rel_notes/deprecation.rst | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ea4cfa7a4..68a63f345 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -17,6 +17,11 @@ Deprecation Notices
   can be got using the ``pip``, or ``pip3``, tool for downloading python
+* build macros: The macros defining RTE_MACHINE_CPUFLAG_* will be removed
+  from the build. The information provided by these macros is available
+  through standard compiler macros. For example, RTE_MACHINE_CPUFLAG_SSE3
+  duplicates the compiler-provided macro __SSE3__.
 * kvargs: The function ``rte_kvargs_process`` will get a new parameter
   for returning key match count. It will ease handling of no-match case.

  reply	other threads:[~2020-08-05 14:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 14:21 [dpdk-dev] [PATCH 0/1] RFC: remove build-type CPU flag macros Bruce Richardson
2020-08-05 14:21 ` Bruce Richardson [this message]
2020-08-05 14:23   ` [dpdk-dev] [PATCH 1/1] doc: add deprecation notice for CPU build flags Jerin Jacob
2020-08-05 14:57   ` [dpdk-dev] [dpdk-techboard] " Thomas Monjalon
2020-08-05 15:07     ` Bruce Richardson
2020-08-05 15:15       ` Thomas Monjalon
2020-08-05 16:45         ` Bruce Richardson
2020-08-05 17:02           ` Thomas Monjalon
2020-08-06 16:01             ` Thomas Monjalon
2020-08-06 21:41           ` Ferruh Yigit
2020-08-07 13:48             ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200805142141.32337-2-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=techboard@dpdk.org \


* 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).