From: Bart Van Assche <Bart.VanAssche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: "fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
<fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "kbuild-all-JC7UmRfGjtg@public.gmane.org"
<kbuild-all-JC7UmRfGjtg@public.gmane.org>,
"andrew.boyer-8PEkshWhKlo@public.gmane.org"
<andrew.boyer-8PEkshWhKlo@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org"
<leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [rdma:k.o/for-4.11 15/22] include/linux/compiler.h:518:38: error: call to '__compiletime_assert_126' declared with attribute error: BUILD_BUG_ON failed: !is_power_of_2(RXE_BUF_PER_MAP)
Date: Thu, 12 Jan 2017 17:00:19 +0000 [thread overview]
Message-ID: <1484240405.2720.3.camel@sandisk.com> (raw)
In-Reply-To: <201701121638.6esoHrp2%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On Thu, 2017-01-12 at 16:50 +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git k.o/for-4.11
> head: c5540a0195ec65e2ab9fcc4bde958db2cc66550c
> commit: 43553b47c3124e7f4a9f115cff9db513b35a5e0a [15/22] IB/rxe: Issue warnings once
> config: i386-randconfig-c0-01121610 (attached as .config)
> compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
> reproduce:
> git checkout 43553b47c3124e7f4a9f115cff9db513b35a5e0a
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All error/warnings (new ones prefixed by >>):
>
> In file included from include/uapi/linux/stddef.h:1:0,
> from include/linux/stddef.h:4,
> from include/uapi/linux/posix_types.h:4,
> from include/uapi/linux/types.h:13,
> from include/linux/types.h:5,
> from include/linux/list.h:4,
> from include/linux/module.h:9,
> from drivers/infiniband/sw/rxe/rxe.h:42,
> from drivers/infiniband/sw/rxe/rxe_mr.c:34:
> drivers/infiniband/sw/rxe/rxe_mr.c: In function 'rxe_mem_alloc.isra.3':
> > > include/linux/compiler.h:518:38: error: call to '__compiletime_assert_126' declared with attribute error: BUILD_BUG_ON failed: !is_power_of_2(RXE_BUF_PER_MAP)
>
> _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
> ^
> include/linux/compiler.h:501:4: note: in definition of macro '__compiletime_assert'
> prefix ## suffix(); \
> ^
> include/linux/compiler.h:518:2: note: in expansion of macro '_compiletime_assert'
> _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
> ^
> include/linux/bug.h:54:37: note: in expansion of macro 'compiletime_assert'
> #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
> ^
> include/linux/bug.h:78:2: note: in expansion of macro 'BUILD_BUG_ON_MSG'
> BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
> ^
> > > drivers/infiniband/sw/rxe/rxe_mr.c:126:2: note: in expansion of macro 'BUILD_BUG_ON'
>
> BUILD_BUG_ON(!is_power_of_2(RXE_BUF_PER_MAP));
> ^
Hello Wu,
make ARCH=i386 M=drivers/infiniband/sw/rxe succeeds on my development system
with the .config that was attached to your e-mail and with gcc 6.2.1. Do you
think the above indicate a bug in the kbuild test robot infrastructure?
Thanks,
Bart.--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-01-12 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 8:50 [rdma:k.o/for-4.11 15/22] include/linux/compiler.h:518:38: error: call to '__compiletime_assert_126' declared with attribute error: BUILD_BUG_ON failed: !is_power_of_2(RXE_BUF_PER_MAP) kbuild test robot
[not found] ` <201701121638.6esoHrp2%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-01-12 17:00 ` Bart Van Assche [this message]
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=1484240405.2720.3.camel@sandisk.com \
--to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
--cc=andrew.boyer-8PEkshWhKlo@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.