From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, Thomas Gleixner <tglx@kernel.org>
Subject: [tip:timers/vdso 16/16] include/linux/compiler_types.h:568:5: warning: 'CC_HAS_TYPEOF_UNQUAL' is not defined, evaluates to '0'
Date: Sun, 18 Jan 2026 08:05:56 +0800 [thread overview]
Message-ID: <202601180747.rlQMyHZI-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/vdso
head: adc00a0daf1bb08915bceee9ae73cca682e7d5bb
commit: adc00a0daf1bb08915bceee9ae73cca682e7d5bb [16/16] compiler: Use __typeof_unqual__() for __unqual_scalar_typeof()
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20260118/202601180747.rlQMyHZI-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260118/202601180747.rlQMyHZI-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/oe-kbuild-all/202601180747.rlQMyHZI-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/compiler.h:5,
from include/linux/export.h:5,
from arch/alpha/lib/divide.S:49:
>> include/linux/compiler_types.h:568:5: warning: 'CC_HAS_TYPEOF_UNQUAL' is not defined, evaluates to '0' [-Wundef]
568 | #if CC_HAS_TYPEOF_UNQUAL || defined(__CHECKER__)
| ^~~~~~~~~~~~~~~~~~~~
vim +568 include/linux/compiler_types.h
564
565 /*
566 * Use __typeof_unqual__() when available.
567 */
> 568 #if CC_HAS_TYPEOF_UNQUAL || defined(__CHECKER__)
569 # define USE_TYPEOF_UNQUAL 1
570 #endif
571
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-18 0:06 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=202601180747.rlQMyHZI-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/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