From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Yury Norov <yury.norov@gmail.com>,
Alexander Lobakin <alexandr.lobakin@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [kbuild-all] Re: [norov:fns 7/19] include/linux/compiler_types.h:352:45: error: call to '__compiletime_assert_600' declared with attribute error: BUILD_BUG_ON failed: !__builtin_constant_p(res)
Date: Mon, 27 Jun 2022 13:01:41 +0800 [thread overview]
Message-ID: <0b0027a2-797f-4e59-5d3c-820223075536@intel.com> (raw)
In-Reply-To: <YrSccxLBlrJ3DyTx@yury-laptop>
On 6/24/2022 1:01 AM, Yury Norov wrote:
> On Thu, Jun 23, 2022 at 01:08:20PM +0200, Alexander Lobakin wrote:
>> From: kernel test robot <lkp@intel.com>
>> Date: Thu, 23 Jun 2022 01:16:29 +0800
>>
>> Hi Yury,
>>
>>> tree: https://github.com/norov/linux fns
>>> head: dc85542660535a9072c3b98819f4b80ff182b92a
>>> commit: 2f52f0373b1a1bcf54a4aedc202518f6bed4c74f [7/19] lib: test_bitmap: add compile-time optimization/evaluations assertions
>>> config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220623/202206230121.wlBiPZcR-lkp@intel.com/config)
>>> compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
>>> reproduce (this is a W=1 build):
>>> # https://github.com/norov/linux/commit/2f52f0373b1a1bcf54a4aedc202518f6bed4c74f
>>> git remote add norov https://github.com/norov/linux
>>> git fetch --no-tags norov fns
>>> git checkout 2f52f0373b1a1bcf54a4aedc202518f6bed4c74f
>>> # save the config file
>>> mkdir build_dir && cp config build_dir/.config
>>> make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
>>
>> Can't reproduce it at all on x86_64 with the attached config, were
>> there any other changes maybe that could cause this?
>
> This is my working branch, and it shouldn't be that loud. But
> anyways...
Hi Yury,
Sorry for the inconvenience, we'll only send reports to you privately
in future.
Best Regards,
Rong Chen
>
> There are some patches on top of your series. This is my
> work-in-progress. If you think it's not relevant, please ignore
> this.
>
> Thanks,
> Yury
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
>
prev parent reply other threads:[~2022-06-27 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 17:16 kernel test robot
2022-06-23 11:08 ` Alexander Lobakin
2022-06-23 17:01 ` Yury Norov
2022-06-27 5:01 ` Chen, Rong A [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=0b0027a2-797f-4e59-5d3c-820223075536@intel.com \
--to=rong.a.chen@intel.com \
--cc=alexandr.lobakin@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=yury.norov@gmail.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
all inboxes | Powered by JetHome®