From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Youling Tang <tangyouling@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: build failure of next-20221005 due to 9dcf746befa7 ("LoongArch: Use generic BUG() handler")
Date: Wed, 5 Oct 2022 12:54:05 +0100 [thread overview]
Message-ID: <Yz1wXUklaN66j8Lt@debian> (raw)
Hi All,
The builds of loongarch allmodconfig have failed to build next-20221005
with error:
./arch/loongarch/include/asm/cmpxchg.h: In function '__cmpxchg':
././include/linux/compiler_types.h:357:45: error: call to '__compiletime_assert_2' declared with attribute error: BUILD_BUG failed
357 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^
././include/linux/compiler_types.h:338:25: note: in definition of macro '__compiletime_assert'
338 | prefix ## suffix(); \
| ^~~~~~
././include/linux/compiler_types.h:357:9: note: in expansion of macro '_compiletime_assert'
357 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^~~~~~~~~~~~~~~~~~~
./include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^~~~~~~~~~~~~~~~~~
./include/linux/build_bug.h:59:21: note: in expansion of macro 'BUILD_BUG_ON_MSG'
59 | #define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
| ^~~~~~~~~~~~~~~~
./arch/loongarch/include/asm/cmpxchg.h:179:17: note: in expansion of macro 'BUILD_BUG'
179 | BUILD_BUG();
| ^~~~~~~~~
git bisect pointed to 9dcf746befa7 ("LoongArch: Use generic BUG() handler")
I will be happy to test any patch or provide any extra log if needed.
--
Regards
Sudip
reply other threads:[~2022-10-05 11:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Yz1wXUklaN66j8Lt@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=chenhuacai@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=tangyouling@loongson.cn \
/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