From: Jason Gunthorpe <jgg@nvidia.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: kernel test robot <lkp@intel.com>,
Nathan Chancellor <nathan@kernel.org>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com
Subject: Re: drivers/infiniband/hw/qib/qib_sysfs.c:413:1: error: static_assert expression is not an integral constant expression
Date: Mon, 13 Sep 2021 15:38:13 -0300 [thread overview]
Message-ID: <20210913183813.GY2505917@nvidia.com> (raw)
In-Reply-To: <CAKwvOdnGaVb1XGwYpNK_3zAEyZ0JC1SDjC1UzzFEH=d_Mdi7Fw@mail.gmail.com>
On Mon, Sep 13, 2021 at 10:00:02AM -0700, Nick Desaulniers wrote:
> > This macro would like to know that the passed in member name has a u64
> > type, all the things I've come up with fail on clang - but many work
> > fine on gcc. Frankly I think this case is a clang bug myself..
>
> Perhaps, though this assertion looks a bit like offsetof() to me. I
> wonder if that can help here?
The assertion would logically like to be this:
static_assert(typecheck(((struct qib_port *)0)->N, u64))
Which doesn't compile because typecheck is not a constexpr :\
typecheck also can't be used as a build bug on zero in the initializer
for the same reason.
My original attempt was
.counter = &((struct qib_ibport *)0)->rvp.n_##N - (u64 *)0, \
Which is fairly simple opencoding of offsetof_end but clang whines
overly pedantically that NULL subtraction is undefined behavior.
The current version is this:
static_assert(&((struct qib_ibport *)0)->rvp.n_##N != (u64 *)NULL);
Which *should* be perfectly fine, but clang explodes for some reason
complaining about -> on NULL. I think it is broken and doesn't
understand that this -> is not an actual deref but pointer/type logic,
much like this:
#define sizeof_field(TYPE, MEMBER) sizeof((((TYPE *)0)->MEMBER))
Which does work.
So to my mind clang is being buggy, and I'm probably going to just
delete the line and a give up on type checking here unless someone has
a better idea.
Jason
next prev parent reply other threads:[~2021-09-13 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 12:17 drivers/infiniband/hw/qib/qib_sysfs.c:413:1: error: static_assert expression is not an integral constant expression kernel test robot
2021-09-13 16:53 ` Jason Gunthorpe
2021-09-13 17:00 ` Nick Desaulniers
2021-09-13 18:38 ` Jason Gunthorpe [this message]
2021-09-13 18:53 ` Nathan Chancellor
2021-09-13 19:02 ` Jason Gunthorpe
2021-09-13 19:13 ` Nathan Chancellor
2021-09-13 19:16 ` Jason Gunthorpe
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=20210913183813.GY2505917@nvidia.com \
--to=jgg@nvidia.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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