From: Arnd Bergmann <arnd@arndb.de> To: Nathan Chancellor <natechancellor@gmail.com> Cc: Heiko Stuebner <heiko@sntech.de>, arm-soc <arm@kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, "open list:ARM/Rockchip SoC support" <linux-rockchip@lists.infradead.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, clang-built-linux <clang-built-linux@googlegroups.com>, Nick Desaulniers <ndesaulniers@google.com>, Nathan Huckleberry <nhuck@google.com> Subject: Re: [PATCH] soc: rockchip: work around clang warning Date: Wed, 3 Jul 2019 19:58:08 +0200 [thread overview] Message-ID: <CAK8P3a098AZfkz0bxfgN_XXk7QSQYi1V-EEmqLjQPjzR7986aA@mail.gmail.com> (raw) In-Reply-To: <20190703165919.GC118075@archlinux-epyc> On Wed, Jul 3, 2019 at 6:59 PM Nathan Chancellor <natechancellor@gmail.com> wrote: > On Wed, Jul 03, 2019 at 05:30:59PM +0200, Arnd Bergmann wrote: > > clang emits a warning about a negative shift count for an > > unused part of a conditional constant expression: > > > > drivers/soc/rockchip/pm_domains.c:795:21: error: shift count is negative [-Werror,-Wshift-count-negative] > > [RK3328_PD_VIO] = DOMAIN_RK3328(-1, 8, 8, false), > > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > drivers/soc/rockchip/pm_domains.c:129:2: note: expanded from macro 'DOMAIN_RK3328' > > DOMAIN_M(pwr, pwr, req, (req) + 10, req, wakeup) > > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > drivers/soc/rockchip/pm_domains.c:105:33: note: expanded from macro 'DOMAIN_M' > > .status_mask = (status >= 0) ? BIT(status) : 0, \ > > ^~~~~~~~~~~ > > include/linux/bits.h:6:24: note: expanded from macro 'BIT' > > > > This is a bug in clang that will be fixed in the future, but in order > > to build cleanly with clang-8, it would be helpful to shut up this > > warning. This file is the only instance reported by kernelci at the > > moment. > > > > The best solution I could come up with is to move the BIT() usage > > out of the macro into the instantiation, so we can avoid using > > BIT(-1). > > > > Link: https://bugs.llvm.org/show_bug.cgi?id=38789 > > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > > Nick recently mentioned that Nathan was working on a fix on the clang > side. It might be worth holding off on this to see if it can make it > into LLVM 9, which will branch in about two weeks and be released at > the end of August (according to llvm.org). I think fixing it in llvm is a good idea regardless of the workaround. My main goal for the workaround is to get a clean kernelci build again, and it will probably take a little while to move that to a fixed clang-9 build (release or prerelease). > I don't feel strongly about it though so if this is going in: > > Reviewed-by: Nathan Chancellor <natechancellor@gmail.com> Thanks! Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de> To: Nathan Chancellor <natechancellor@gmail.com> Cc: Heiko Stuebner <heiko@sntech.de>, clang-built-linux <clang-built-linux@googlegroups.com>, Nick Desaulniers <ndesaulniers@google.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Nathan Huckleberry <nhuck@google.com>, "open list:ARM/Rockchip SoC support" <linux-rockchip@lists.infradead.org>, arm-soc <arm@kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH] soc: rockchip: work around clang warning Date: Wed, 3 Jul 2019 19:58:08 +0200 [thread overview] Message-ID: <CAK8P3a098AZfkz0bxfgN_XXk7QSQYi1V-EEmqLjQPjzR7986aA@mail.gmail.com> (raw) In-Reply-To: <20190703165919.GC118075@archlinux-epyc> On Wed, Jul 3, 2019 at 6:59 PM Nathan Chancellor <natechancellor@gmail.com> wrote: > On Wed, Jul 03, 2019 at 05:30:59PM +0200, Arnd Bergmann wrote: > > clang emits a warning about a negative shift count for an > > unused part of a conditional constant expression: > > > > drivers/soc/rockchip/pm_domains.c:795:21: error: shift count is negative [-Werror,-Wshift-count-negative] > > [RK3328_PD_VIO] = DOMAIN_RK3328(-1, 8, 8, false), > > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > drivers/soc/rockchip/pm_domains.c:129:2: note: expanded from macro 'DOMAIN_RK3328' > > DOMAIN_M(pwr, pwr, req, (req) + 10, req, wakeup) > > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > drivers/soc/rockchip/pm_domains.c:105:33: note: expanded from macro 'DOMAIN_M' > > .status_mask = (status >= 0) ? BIT(status) : 0, \ > > ^~~~~~~~~~~ > > include/linux/bits.h:6:24: note: expanded from macro 'BIT' > > > > This is a bug in clang that will be fixed in the future, but in order > > to build cleanly with clang-8, it would be helpful to shut up this > > warning. This file is the only instance reported by kernelci at the > > moment. > > > > The best solution I could come up with is to move the BIT() usage > > out of the macro into the instantiation, so we can avoid using > > BIT(-1). > > > > Link: https://bugs.llvm.org/show_bug.cgi?id=38789 > > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > > Nick recently mentioned that Nathan was working on a fix on the clang > side. It might be worth holding off on this to see if it can make it > into LLVM 9, which will branch in about two weeks and be released at > the end of August (according to llvm.org). I think fixing it in llvm is a good idea regardless of the workaround. My main goal for the workaround is to get a clean kernelci build again, and it will probably take a little while to move that to a fixed clang-9 build (release or prerelease). > I don't feel strongly about it though so if this is going in: > > Reviewed-by: Nathan Chancellor <natechancellor@gmail.com> Thanks! Arnd _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-03 17:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-03 15:30 [PATCH] soc: rockchip: work around clang warning Arnd Bergmann 2019-07-03 15:30 ` Arnd Bergmann 2019-07-03 15:30 ` Arnd Bergmann 2019-07-03 16:59 ` Nathan Chancellor 2019-07-03 16:59 ` Nathan Chancellor 2019-07-03 17:58 ` Arnd Bergmann [this message] 2019-07-03 17:58 ` Arnd Bergmann 2019-07-03 17:58 ` Arnd Bergmann 2019-07-04 2:20 ` Olof Johansson 2019-07-04 2:20 ` Olof Johansson
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=CAK8P3a098AZfkz0bxfgN_XXk7QSQYi1V-EEmqLjQPjzR7986aA@mail.gmail.com \ --to=arnd@arndb.de \ --cc=arm@kernel.org \ --cc=clang-built-linux@googlegroups.com \ --cc=heiko@sntech.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=natechancellor@gmail.com \ --cc=ndesaulniers@google.com \ --cc=nhuck@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.