From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>, Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>
Cc: linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
torvalds@linux-foundation.org, loongarch@lists.linux.dev
Subject: mainline build failure for loongarch allmodconfig with gcc-12
Date: Tue, 23 Aug 2022 09:34:31 +0100 [thread overview]
Message-ID: <YwSRFzQQKAXP2ncp@debian> (raw)
Hi All,
I have been trying to build loongarch as part of my nightly builds, and
I can build loongson3_defconfig without any error. But allmodconfig fails
with the error:
In function '__cmpxchg',
inlined from 'ssh_seq_next' at drivers/platform/surface/aggregator/controller.c:61:9,
inlined from 'ssam_request_write_data' at drivers/platform/surface/aggregator/controller.c:1483:8,
inlined from 'ssam_request_sync_with_buffer' at drivers/platform/surface/aggregator/controller.c:1761:8:
././include/linux/compiler_types.h:354:45: error: call to '__compiletime_assert_9' declared with attribute error: BUILD_BUG failed
354 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^
././include/linux/compiler_types.h:335:25: note: in definition of macro '__compiletime_assert'
335 | prefix ## suffix(); \
| ^~~~~~
././include/linux/compiler_types.h:354:9: note: in expansion of macro '_compiletime_assert'
354 | _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:83:17: note: in expansion of macro 'BUILD_BUG'
83 | BUILD_BUG();
| ^~~~~~~~~
I will be happy to test any patch or provide any extra log if needed.
--
Regards
Sudip
next reply other threads:[~2022-08-23 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 8:34 Sudip Mukherjee (Codethink) [this message]
2022-08-23 18:09 ` mainline build failure for loongarch allmodconfig with gcc-12 Linus Torvalds
2022-08-24 1:38 ` Huacai Chen
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=YwSRFzQQKAXP2ncp@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=loongarch@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=torvalds@linux-foundation.org \
--cc=trix@redhat.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