DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/5] add portable version of __builtin_add_overflow
Date: Thu, 2 Jan 2025 15:51:55 -0800	[thread overview]
Message-ID: <20250102155155.3c7545f3@pi5> (raw)
In-Reply-To: <1735857169-19131-1-git-send-email-andremue@linux.microsoft.com>

On Thu,  2 Jan 2025 14:32:43 -0800
Andre Muezerie <andremue@linux.microsoft.com> wrote:

> __builtin_add_overflow is gcc specific. There's a need for a portable
> version that can also be used with other compilers.
> 
> Andre Muezerie (5):
>   maintainers: add portable version of __builtin_add_overflow
>   lib/eal: add portable version of __builtin_add_overflow
>   doc/api: add portable version of __builtin_add_overflow
>   drivers/net: use portable version of __builtin_add_overflow
>   app/test: add tests for portable versions of __builtin_add_overflow
> 
>  MAINTAINERS                    |   1 +
>  app/test/meson.build           |   1 +
>  app/test/test_math.c           | 125 +++++++++++++++++++++++++++++++++
>  doc/api/doxy-api-index.md      |   1 +
>  drivers/net/ice/base/ice_nvm.c |   9 ++-
>  lib/eal/include/meson.build    |   1 +
>  lib/eal/include/rte_math.h     |  42 +++++++++++
>  7 files changed, 175 insertions(+), 5 deletions(-)
>  create mode 100644 app/test/test_math.c
>  create mode 100644 lib/eal/include/rte_math.h
> 
> --
> 2.47.0.vfs.0.3
> 

You should add _builtin_add_overflow into the checkpatch naughty list.
Or maybe all the _builtin_XXX functions?

  parent reply	other threads:[~2025-01-02 23:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 22:32 Andre Muezerie
2025-01-02 22:32 ` [PATCH 1/5] maintainers: " Andre Muezerie
2025-01-02 22:32 ` [PATCH 2/5] lib/eal: " Andre Muezerie
2025-01-03  8:19   ` Morten Brørup
2025-01-03 20:38     ` Andre Muezerie
2025-01-02 22:32 ` [PATCH 3/5] doc/api: " Andre Muezerie
2025-01-02 22:32 ` [PATCH 4/5] drivers/net: use " Andre Muezerie
2025-01-02 22:32 ` [PATCH 5/5] app/test: add tests for portable versions " Andre Muezerie
2025-01-02 23:51 ` Stephen Hemminger [this message]
2025-01-03  0:15   ` [PATCH 0/5] add portable version " Andre Muezerie
2025-01-03  0:41     ` Andre Muezerie
2025-01-03 20:39 ` [PATCH v2 " Andre Muezerie
2025-01-03 20:39   ` [PATCH v2 1/5] maintainers: " Andre Muezerie
2025-01-03 20:39   ` [PATCH v2 2/5] lib/eal: " Andre Muezerie
2025-01-06 11:07     ` Bruce Richardson
2025-01-06 11:21       ` Morten Brørup
2025-01-06 11:34         ` Bruce Richardson
2025-01-06 11:58           ` Morten Brørup
2025-01-03 20:39   ` [PATCH v2 3/5] doc/api: " Andre Muezerie
2025-01-03 20:39   ` [PATCH v2 4/5] drivers/net: use " Andre Muezerie
2025-01-03 20:39   ` [PATCH v2 5/5] app/test: add tests for " Andre Muezerie

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=20250102155155.3c7545f3@pi5 \
    --to=stephen@networkplumber.org \
    --cc=andremue@linux.microsoft.com \
    --cc=dev@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).