public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
	kernel test robot <lkp@intel.com>, <llvm@lists.linux.dev>,
	<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	Yury Norov <yury.norov@gmail.com>
Subject: Re: lib/test_bitmap.c:920:2: error: call to __compiletime_assert_372 declared with 'error' attribute: BUILD_BUG_ON failed: !__builtin_constant_p(res)
Date: Mon, 26 Jun 2023 13:57:46 +0200	[thread overview]
Message-ID: <0e50e878-3944-c57c-1dbf-10d260f05afc@intel.com> (raw)
In-Reply-To: <ZJlNMwzlt2MGTvBp@smile.fi.intel.com>

From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: Mon, 26 Jun 2023 11:32:51 +0300

> On Sun, Jun 25, 2023 at 05:12:36AM +0800, kernel test robot wrote:
>> Hi Alexander,
>>
>> FYI, the error/warning still remains.
> 
> Alexander, do you have anything to present to fix this? Or is your plan to send
> something after v6.5-rc1?

Hi,
I was waiting for an email from Nick (or some further update of the
GitHub issue page) to clarify whether the compiler should be fixed or I
should work around this in the code. If the latter, I could send a fix
this week, so that it could even hit the bitmap pull request.

Thanks,
Olek

  reply	other threads:[~2023-06-26 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 21:12 lib/test_bitmap.c:920:2: error: call to __compiletime_assert_372 declared with 'error' attribute: BUILD_BUG_ON failed: !__builtin_constant_p(res) kernel test robot
2023-06-26  8:32 ` Andy Shevchenko
2023-06-26 11:57   ` Alexander Lobakin [this message]
2023-06-26 13:26     ` Andy Shevchenko

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=0e50e878-3944-c57c-1dbf-10d260f05afc@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=ndesaulniers@google.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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