From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, <roretzla@linux.microsoft.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: Re: [PATCH] remove wrappers for GCC < 4.8
Date: Thu, 24 Aug 2023 10:00:10 +0100 [thread overview]
Message-ID: <ZOccGmum9fSpwsPH@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20230824083034.806773-1-david.marchand@redhat.com>
On Thu, Aug 24, 2023 at 10:30:34AM +0200, David Marchand wrote:
> As we made our move to C11, GCC requirements has been bumped.
> Wrappers for old versions of GCC can be dropped.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> lib/eal/arm/include/rte_byteorder.h | 19 -------------------
> lib/eal/arm/include/rte_vect.h | 12 ------------
> lib/eal/include/generic/rte_byteorder.h | 2 --
> lib/eal/include/rte_debug.h | 4 ----
> lib/eal/ppc/include/rte_byteorder.h | 9 ---------
> lib/eal/x86/include/rte_byteorder.h | 8 --------
> lib/eal/x86/include/rte_vect.h | 9 +--------
> lib/log/rte_log.h | 4 ----
> 8 files changed, 1 insertion(+), 66 deletions(-)
>
I think there are checks for GCC_VERSION > 40306 (i.e. gcc 4.3) in
rte_lru_x86.h that can be removed too. Otherwise,
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2023-08-24 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 8:30 David Marchand
2023-08-24 8:52 ` David Marchand
2023-08-25 16:14 ` Tyler Retzlaff
2023-08-26 8:33 ` David Marchand
2023-08-24 9:00 ` Bruce Richardson [this message]
2023-08-24 9:33 ` [PATCH v2] remove compatibility " David Marchand
2023-08-25 8:37 ` 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=ZOccGmum9fSpwsPH@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=roretzla@linux.microsoft.com \
--cc=ruifeng.wang@arm.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).