From: Anton Blanchard <anton@samba.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Nicholas Piggin <npiggin@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BUILD_BUG_ON(!__builtin_constant_p(feature)) breaks bcc trace tool
Date: Sat, 21 Jan 2017 20:49:48 +1100 [thread overview]
Message-ID: <20170121204948.742f89bf@kryten> (raw)
In-Reply-To: <20170121120339.1c774b28@kryten>
Hi,
> We added:
>
> BUILD_BUG_ON(!__builtin_constant_p(feature))
>
> to cpu_has_feature() and mmu_has_feature() in order to catch usage
> issues (such as cpu_has_feature(cpu_has_feature(X)). Unfortunately
> LLVM isn't smart enough to resolve this, and it errors out.
>
> I work around it in my clang/LLVM builds of the kernel, but I have
> just discovered that it causes a lot of issues for the bcc (eBPF)
> trace tool (which uses LLVM).
>
> How should we work around this? Wrap the checks in !clang perhaps?
Looks like it's a weakness in LLVM with inlining:
#include <assert.h>
#if 1
static inline void foo(unsigned long x)
{
assert(__builtin_constant_p(x));
}
#else
#define foo(X) assert(__builtin_constant_p(X))
#endif
int main(void)
{
foo(1);
return 0;
}
And there is an old bug on it:
https://llvm.org/bugs/show_bug.cgi?id=4898
Anton
next prev parent reply other threads:[~2017-01-21 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 1:03 BUILD_BUG_ON(!__builtin_constant_p(feature)) breaks bcc trace tool Anton Blanchard
2017-01-21 9:49 ` Anton Blanchard [this message]
2017-01-24 6:15 ` Michael Ellerman
2017-01-24 9:45 ` Arnd Bergmann
2017-01-25 10:35 ` David Laight
2017-01-25 15:44 ` Arnd Bergmann
2017-01-24 5:36 ` Michael Ellerman
2017-01-24 10:47 ` Naveen N. Rao
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=20170121204948.742f89bf@kryten \
--to=anton@samba.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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).