From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH v2] common/sfc: replace out of bounds condition with static_assert
Date: Wed, 7 Feb 2024 14:34:42 -0800 [thread overview]
Message-ID: <20240207143442.0aba4ebe@hermes.local> (raw)
In-Reply-To: <a8c840b3-9e9a-401f-900f-e3bdf27875e1@amd.com>
On Wed, 7 Feb 2024 19:10:37 +0000
Ferruh Yigit <ferruh.yigit@amd.com> wrote:
> On 1/19/2024 10:13 PM, Stephen Hemminger wrote:
> > The sfc base code had its own definition of static assertions
> > using the out of bound array access hack. Replace it with a
> > static_assert like rte_common.h.
> >
> > Fixes: f67e4719147d ("net/sfc/base: fix coding style")
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > Acked-by: Morten Brørup <mb@smartsharesystems.com>
> > ---
> > v2 - add assert.h to make sure it works in other environments
> >
> > drivers/common/sfc_efx/base/efx.h | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/common/sfc_efx/base/efx.h b/drivers/common/sfc_efx/base/efx.h
> > index 3312c2fa8f81..38f2aed3e336 100644
> > --- a/drivers/common/sfc_efx/base/efx.h
> > +++ b/drivers/common/sfc_efx/base/efx.h
> > @@ -7,6 +7,8 @@
> > #ifndef _SYS_EFX_H
> > #define _SYS_EFX_H
> >
> > +#include <assert.h>
> > +
> > #include "efx_annote.h"
> > #include "efsys.h"
> > #include "efx_types.h"
> > @@ -17,8 +19,8 @@
> > extern "C" {
> > #endif
> >
> > -#define EFX_STATIC_ASSERT(_cond) \
> > - ((void)sizeof (char[(_cond) ? 1 : -1]))
> > +#define EFX_STATIC_ASSERT(_cond) \
> > + do { static_assert((_cond), "assert failed" #_cond); } while (0)
> >
> > #define EFX_ARRAY_SIZE(_array) \
> > (sizeof (_array) / sizeof ((_array)[0]))
>
> Getting following build error with clang:
What version of clang?
It works for me with clang 16.0.6
next prev parent reply other threads:[~2024-02-07 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 20:18 [PATCH] " Stephen Hemminger
2024-01-18 23:05 ` Morten Brørup
2024-02-13 7:47 ` Andrew Rybchenko
2024-01-19 22:13 ` [PATCH v2] " Stephen Hemminger
2024-01-20 7:53 ` Morten Brørup
2024-02-07 19:10 ` Ferruh Yigit
2024-02-07 22:34 ` Stephen Hemminger [this message]
2024-02-07 22:36 ` Stephen Hemminger
2024-02-07 23:30 ` Ferruh Yigit
2024-02-11 17:41 ` Stephen Hemminger
2024-02-11 22:24 ` [PATCH] " Stephen Hemminger
2024-02-12 5:48 ` [PATCH v4] " Stephen Hemminger
2024-02-12 12:09 ` Ferruh Yigit
2024-02-13 9:39 ` Ferruh Yigit
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=20240207143442.0aba4ebe@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=mb@smartsharesystems.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).