public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Alexey Dobriyan" <adobriyan@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Andrii Nakryiko" <andrii@kernel.org>,
	"Arnd Bergmann" <arnd@kernel.org>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dan Williams" <dan.j.williams@intel.com>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"David Laight" <David.Laight@aculab.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Dinh Nguyen" <dinguyen@kernel.org>,
	"Eduard Zingerman" <eddyz87@gmail.com>,
	"Gatlin Newhouse" <gatlin.newhouse@gmail.com>,
	"Hao Luo" <haoluo@google.com>, "Ingo Molnar" <mingo@redhat.com>,
	"Jakub Sitnicki" <jakub@cloudflare.com>,
	"Jan Hendrik Farr" <kernel@jfarr.cc>,
	"Jason Wang" <jasowang@redhat.com>,
	"Jiri Olsa" <jolsa@kernel.org>,
	"John Fastabend" <john.fastabend@gmail.com>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	"Josh Poimboeuf" <jpoimboe@kernel.org>,
	"KP Singh" <kpsingh@kernel.org>, "Kees Cook" <kees@kernel.org>,
	"Luc Van Oostenryck" <luc.vanoostenryck@gmail.com>,
	"Marc Herbert" <Marc.Herbert@linux.intel.com>,
	"Martin KaFai Lau" <martin.lau@linux.dev>,
	"Mateusz Guzik" <mjguzik@gmail.com>,
	"Michal Luczaj" <mhal@rbox.co>, "Miguel Ojeda" <ojeda@kernel.org>,
	"Mykola Lysenko" <mykolal@fb.com>, NeilBrown <neil@brown.name>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Przemek Kitszel" <przemyslaw.kitszel@intel.com>,
	"Sami Tolvanen" <samitolvanen@google.com>,
	"Shuah Khan" <shuah@kernel.org>, "Song Liu" <song@kernel.org>,
	"Stanislav Fomichev" <sdf@fomichev.me>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Thorsten Blum" <thorsten.blum@linux.dev>,
	"Uros Bizjak" <ubizjak@gmail.com>,
	"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	"Yafang Shao" <laoar.shao@gmail.com>,
	"Ye Bin" <yebin10@huawei.com>,
	"Yonghong Song" <yonghong.song@linux.dev>,
	"Yufeng Wang" <wangyufeng@kylinos.cn>,
	bpf@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-sparse@vger.kernel.org, virtualization@lists.linux.dev,
	x86@kernel.org
Subject: Re: [GIT PULL] __auto_type conversion for v6.19-rc1
Date: Tue, 9 Dec 2025 09:07:07 +0000	[thread overview]
Message-ID: <20251209090707.GV1712166@ZenIV> (raw)
In-Reply-To: <87F4003B-5011-49EF-A807-CEA094EA0DAC@zytor.com>

On Mon, Dec 08, 2025 at 07:28:53PM -0800, H. Peter Anvin wrote:

> Yeah... the C committee even admitted they botched the spec; the intent was for it to work "exactly like gcc __auto_type"...

BTW, speaking of C23 fun that is supported by gcc 8, but not by sparse:
__has_include().

Do we want it?  At the moment nothing in the kernel is using that thing.
The main case for that would be <asm/something_optional.h>, and mostly
it's dealt with by dummy asm-generic/something_optional.h and mandatory-y
in asm-generic/Kbuild, but there are at least some cases where we have
it guarded by ifdef, a-la
#ifdef CONFIG_ARCH_HAS_ELFCORE_COMPAT
#include <asm/elfcore-compat.h>
#endif

Linus?  Seeing that I'm touching pre-process.c anyway for the sake of
__VA_OPT__, adding that thing ought to be reasonably easy - a bit of
work in expression_value(), the tricky part being where to stop the
scan: __has_include(< => scan to > and demand ) after it,
__has_include(string literal => demand ) after it,
__has_include(anything else => scan to matching ), and expand the
collected tokens.  The same dodge we use for #include ("anything
potentially fishy in header-name and it's an UB, so one can
simulate it with other pp-tokens") works here...

  reply	other threads:[~2025-12-09  9:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 23:55 [GIT PULL] __auto_type conversion for v6.19-rc1 H. Peter Anvin
2025-12-09  0:11 ` pr-tracker-bot
2025-12-09  0:20   ` Linus Torvalds
2025-12-09  0:21     ` H. Peter Anvin
2025-12-09  3:33       ` Linus Torvalds
2025-12-09  8:00         ` Konstantin Ryabitsev
2025-12-09  0:25 ` Al Viro
2025-12-09  0:28   ` H. Peter Anvin
2025-12-09  3:22     ` Al Viro
2025-12-09  3:28       ` H. Peter Anvin
2025-12-09  9:07         ` Al Viro [this message]
2025-12-09 20:40           ` Linus Torvalds
2025-12-09  7:26 ` Linus Torvalds

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=20251209090707.GV1712166@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=David.Laight@aculab.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Marc.Herbert@linux.intel.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=arnd@kernel.org \
    --cc=ast@kernel.org \
    --cc=bp@alien8.de \
    --cc=bpf@vger.kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=daniel@iogearbox.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=dinguyen@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=eddyz87@gmail.com \
    --cc=eperezma@redhat.com \
    --cc=gatlin.newhouse@gmail.com \
    --cc=haoluo@google.com \
    --cc=hpa@zytor.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jakub@cloudflare.com \
    --cc=jasowang@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=kees@kernel.org \
    --cc=kernel@jfarr.cc \
    --cc=kpsingh@kernel.org \
    --cc=laoar.shao@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=mhal@rbox.co \
    --cc=mingo@redhat.com \
    --cc=mjguzik@gmail.com \
    --cc=mst@redhat.com \
    --cc=mykolal@fb.com \
    --cc=neil@brown.name \
    --cc=ojeda@kernel.org \
    --cc=peterz@infradead.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=samitolvanen@google.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=thorsten.blum@linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=ubizjak@gmail.com \
    --cc=virtualization@lists.linux.dev \
    --cc=wangyufeng@kylinos.cn \
    --cc=x86@kernel.org \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=yebin10@huawei.com \
    --cc=yonghong.song@linux.dev \
    /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