From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: Aaron Conole <aconole@redhat.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
techboard@dpdk.org, dev@dpdk.org
Subject: Re: [PATCH v3] build: announce requirement for C11
Date: Fri, 19 May 2023 13:01:42 -0700 [thread overview]
Message-ID: <20230519200142.GA22897@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <f7t8rdkpl8q.fsf@redhat.com>
On Fri, May 19, 2023 at 08:19:01AM -0400, Aaron Conole wrote:
> Resending - this time to the correct list.
>
> Bruce Richardson <bruce.richardson@intel.com> writes:
> > Add a deprecation notice informing users that we will require a C11
> > compiler from 23.11 release onwards. This requirement was agreed by
> > technical board to enable use of newer C language features, e.g.
> > standard atomics. [1]
> >
> > [1]
> > http://inbox.dpdk.org/dev/DBAPR08MB58148CEC3E1454E8848A938998AB9@DBAPR08MB5814.eurprd08.prod.outlook.com/
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> >
> > ---
> >
> > V3:
> > - add additional detail following discussion on-list
> >
> > V2:
> > - add requirement for stdatomics
> > - fix sphinx formatting
> > ---
> > doc/guides/rel_notes/deprecation.rst | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
>
> Acked-by: Aaron Conole <aconole@redhat.com>
>
> Per the meeting, I guess we're still waiting on the patches that
> introduce the stdatomic calls, right? At least, I probably missed it
> when looking on the patchwork instance.
the following series need merge, they remove some old rte atomics and
normalize the use of gcc builtins to set the tree up to be more easily
converted to stdatomics.
https://patchwork.dpdk.org/project/dpdk/list/?series=27530
https://patchwork.dpdk.org/project/dpdk/list/?series=27552
please review the linked series if you have time, since the impact of
the changes may be broad it would help David and Thomas.
as soon as the above series are merged i will begin submitting the
actual stdatomics series for review.
thanks!
next prev parent reply other threads:[~2023-05-19 20:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 15:14 [PATCH] " Bruce Richardson
2023-05-03 15:35 ` Tyler Retzlaff
2023-05-03 15:37 ` Bruce Richardson
2023-05-03 15:39 ` Ferruh Yigit
2023-05-03 15:45 ` Tyler Retzlaff
2023-05-03 15:57 ` Bruce Richardson
2023-05-03 16:07 ` Tyler Retzlaff
2023-05-03 16:51 ` Ferruh Yigit
2023-05-03 17:30 ` [PATCH v2] " Bruce Richardson
2023-05-04 7:50 ` Mattias Rönnblom
2023-05-04 8:48 ` Bruce Richardson
2023-05-04 15:24 ` Tyler Retzlaff
2023-05-03 21:34 ` [PATCH] " Morten Brørup
2023-05-17 17:34 ` [PATCH v3] " Bruce Richardson
2023-05-19 12:19 ` Aaron Conole
2023-05-19 20:01 ` Tyler Retzlaff [this message]
2023-07-20 8:22 ` Bruce Richardson
2023-07-20 10:56 ` Jerin Jacob
2023-07-28 9:34 ` 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=20230519200142.GA22897@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.com \
--cc=aconole@redhat.com \
--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).