From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb+git@google.com>, <linux-kernel@vger.kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
"Ard Biesheuvel" <ardb@kernel.org>,
"Austin Zheng" <austin.zheng@amd.com>,
"Jun Lei" <jun.lei@amd.com>,
"Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Rodrigo Siqueira" <siqueira@igalia.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/amd: Permit DC_FP_START/END only in non-FP compilation units
Date: Sun, 12 Oct 2025 22:22:15 +0800 [thread overview]
Message-ID: <aOu5l1EM8PnoKEgD@rli9-mobl> (raw)
In-Reply-To: <20251009150621.3886079-2-ardb+git@google.com>
Hi Ard,
kernel test robot noticed the following build errors:
[auto build test ERROR on soc/for-next]
[also build test ERROR on linus/master v6.17 next-20251010]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ard-Biesheuvel/drm-amd-Permit-DC_FP_START-END-only-in-non-FP-compilation-units/20251010-120206
base: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git for-next
patch link: https://lore.kernel.org/r/20251009150621.3886079-2-ardb%2Bgit%40google.com
patch subject: [PATCH] drm/amd: Permit DC_FP_START/END only in non-FP compilation units
:::::: branch date: 14 hours ago
:::::: commit date: 14 hours ago
config: x86_64-randconfig-071-20251010 (https://download.01.org/0day-ci/archive/20251011/202510110219.Z6t2PJbZ-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251011/202510110219.Z6t2PJbZ-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202510110219.Z6t2PJbZ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_wrapper.c:563:2: error: call to '__compiletime_assert_610' declared with 'error' attribute: BUILD_BUG failed
563 | DC_FP_START();
| ^
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.h:38:23: note: expanded from macro 'DC_FP_START'
38 | #define DC_FP_START() BUILD_BUG()
| ^
include/linux/build_bug.h:59:21: note: expanded from macro 'BUILD_BUG'
59 | #define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
| ^
include/linux/build_bug.h:39:37: note: expanded from macro 'BUILD_BUG_ON_MSG'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
include/linux/compiler_types.h:583:2: note: expanded from macro '_compiletime_assert'
583 | __compiletime_assert(condition, msg, prefix, suffix)
| ^
include/linux/compiler_types.h:576:4: note: expanded from macro '__compiletime_assert'
576 | prefix ## suffix(); \
| ^
<scratch space>:39:1: note: expanded from here
39 | __compiletime_assert_610
| ^
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_wrapper.c:615:2: error: call to '__compiletime_assert_612' declared with 'error' attribute: BUILD_BUG failed
615 | DC_FP_START();
| ^
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.h:38:23: note: expanded from macro 'DC_FP_START'
38 | #define DC_FP_START() BUILD_BUG()
| ^
include/linux/build_bug.h:59:21: note: expanded from macro 'BUILD_BUG'
59 | #define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
| ^
include/linux/build_bug.h:39:37: note: expanded from macro 'BUILD_BUG_ON_MSG'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
include/linux/compiler_types.h:583:2: note: expanded from macro '_compiletime_assert'
583 | __compiletime_assert(condition, msg, prefix, suffix)
| ^
include/linux/compiler_types.h:576:4: note: expanded from macro '__compiletime_assert'
576 | prefix ## suffix(); \
| ^
<scratch space>:45:1: note: expanded from here
45 | __compiletime_assert_612
| ^
2 errors generated.
vim +563 drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_wrapper.c
7966f319c66d94 Qingqing Zhuo 2023-07-28 547
269c1d1443d668 Yan Li 2025-05-14 548 bool dml2_validate(const struct dc *in_dc, struct dc_state *context, struct dml2_context *dml2,
269c1d1443d668 Yan Li 2025-05-14 549 enum dc_validate_mode validate_mode)
7966f319c66d94 Qingqing Zhuo 2023-07-28 550 {
7966f319c66d94 Qingqing Zhuo 2023-07-28 551 bool out = false;
7966f319c66d94 Qingqing Zhuo 2023-07-28 552
cc263c3a0c9f38 Joshua Aberback 2024-03-07 553 if (!dml2)
7966f319c66d94 Qingqing Zhuo 2023-07-28 554 return false;
cc263c3a0c9f38 Joshua Aberback 2024-03-07 555 dml2_apply_debug_options(in_dc, dml2);
7966f319c66d94 Qingqing Zhuo 2023-07-28 556
00c391102abc13 Aurabindo Pillai 2024-03-20 557 /* DML2.1 validation path */
00c391102abc13 Aurabindo Pillai 2024-03-20 558 if (dml2->architecture == dml2_architecture_21) {
269c1d1443d668 Yan Li 2025-05-14 559 out = dml21_validate(in_dc, context, dml2, validate_mode);
00c391102abc13 Aurabindo Pillai 2024-03-20 560 return out;
00c391102abc13 Aurabindo Pillai 2024-03-20 561 }
7966f319c66d94 Qingqing Zhuo 2023-07-28 562
366e77cd4923c3 Huacai Chen 2025-03-27 @563 DC_FP_START();
366e77cd4923c3 Huacai Chen 2025-03-27 564
269c1d1443d668 Yan Li 2025-05-14 565 /* Use dml_validate_only for DC_VALIDATE_MODE_ONLY and DC_VALIDATE_MODE_AND_STATE_INDEX path */
269c1d1443d668 Yan Li 2025-05-14 566 if (validate_mode != DC_VALIDATE_MODE_AND_PROGRAMMING)
b02b0fc488ba6e Yan Li 2025-05-21 567 out = dml2_validate_only(context, validate_mode);
7966f319c66d94 Qingqing Zhuo 2023-07-28 568 else
b02b0fc488ba6e Yan Li 2025-05-21 569 out = dml2_validate_and_build_resource(in_dc, context, validate_mode);
366e77cd4923c3 Huacai Chen 2025-03-27 570
366e77cd4923c3 Huacai Chen 2025-03-27 571 DC_FP_END();
366e77cd4923c3 Huacai Chen 2025-03-27 572
7966f319c66d94 Qingqing Zhuo 2023-07-28 573 return out;
7966f319c66d94 Qingqing Zhuo 2023-07-28 574 }
7966f319c66d94 Qingqing Zhuo 2023-07-28 575
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-10-12 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 15:06 [PATCH] drm/amd: Permit DC_FP_START/END only in non-FP compilation units Ard Biesheuvel
2025-10-09 16:19 ` Christian König
2025-10-09 20:40 ` Harry Wentland
2025-10-09 21:27 ` Ard Biesheuvel
2025-10-12 14:22 ` kernel test robot [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=aOu5l1EM8PnoKEgD@rli9-mobl \
--to=lkp@intel.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=austin.zheng@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=jun.lei@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.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;
as well as URLs for NNTP newsgroup(s).