From: Thomas Monjalon <thomas@monjalon.net>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Jerin Jacob <jerinj@marvell.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: Re: [PATCH 00/32] Remove use and definition of RTE_STD_C11 macro
Date: Wed, 30 Aug 2023 19:34:03 +0200 [thread overview]
Message-ID: <2118500.OBFZWjSADL@thomas> (raw)
In-Reply-To: <1691792567-10805-1-git-send-email-roretzla@linux.microsoft.com>
12/08/2023 00:22, Tyler Retzlaff:
> We now document C11 conformant compiler as a minimum, it's not necessary
> to mark C11 feature use with __extension__ to avoid warnings.
Did you check the occurences of __extension__?
I remember at least the case of bit-fields.
Is there any C standard allowing them?
next prev parent reply other threads:[~2023-08-30 17:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 22:22 Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 01/32] timer: remove use of RTE STD C11 macro Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 02/32] stack: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 03/32] security: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 04/32] sched: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 05/32] ring: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 06/32] regexdev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 07/32] rawdev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 08/32] power: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 09/32] pipeline: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 10/32] net: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 11/32] mldev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 12/32] mempool: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 13/32] mbuf: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 14/32] ip_frag: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 15/32] hash: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 16/32] graph: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 17/32] eventdev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 18/32] ethdev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 19/32] dmadev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 20/32] cryptodev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 21/32] examples/ipsec-secgw: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 22/32] examples/ip_pipeline: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 23/32] net/sfc: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 24/32] net/octeontx: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 25/32] net/mlx5: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 26/32] net/mlx4: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 27/32] net/igc: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 28/32] net/avp: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 29/32] dma/idxd: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 30/32] common/mlx5: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 31/32] common/cnxk: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 32/32] eal: remove use and definition " Tyler Retzlaff
2023-08-14 8:40 ` [PATCH 00/32] Remove use and definition of RTE_STD_C11 macro Bruce Richardson
2023-08-14 8:45 ` Morten Brørup
2023-08-14 8:47 ` Morten Brørup
2023-08-16 16:32 ` David Marchand
2023-08-30 17:34 ` Thomas Monjalon [this message]
2023-08-31 23:12 ` Tyler Retzlaff
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=2118500.OBFZWjSADL@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=roretzla@linux.microsoft.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).