From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-techboard] [PATCH 1/1] doc: add deprecation notice for CPU build flags
Date: Wed, 05 Aug 2020 16:57:42 +0200 [thread overview]
Message-ID: <2844470.HTv9E7uqEf@thomas> (raw)
In-Reply-To: <20200805142141.32337-2-bruce.richardson@intel.com>
05/08/2020 16:21, Bruce Richardson:
> 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>
> ---
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> +* 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__.
I see 2 advantages of having alias:
- if 2 compilers differ, we can manage
- we can find all such macros with grep RTE_MACHINE_CPUFLAG
next prev parent reply other threads:[~2020-08-05 14:57 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 ` [dpdk-dev] [PATCH 1/1] doc: add deprecation notice for CPU build flags Bruce Richardson
2020-08-05 14:23 ` Jerin Jacob
2020-08-05 14:57 ` Thomas Monjalon [this message]
2020-08-05 15:07 ` [dpdk-dev] [dpdk-techboard] " 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:
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=2844470.HTv9E7uqEf@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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).