From: Kees Cook <keescook@chromium.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-toolchains@vger.kernel.org, peterz@infradead.org,
hpa@zytor.com, rostedt@goodmis.org, gregkh@linuxfoundation.org,
ndesaulniers@google.com, justinstitt@google.com,
torvalds@linux-foundation.org, linux-hardening@vger.kernel.org
Subject: Re: A few proposals from the C standards committee
Date: Tue, 23 Jan 2024 14:39:58 -0800 [thread overview]
Message-ID: <202401231437.171F50B769@keescook> (raw)
In-Reply-To: <9162660e-2d6b-47a3-bfa2-77bfc55c817b@paulmck-laptop>
On Tue, Jan 23, 2024 at 08:46:13AM -0800, Paul E. McKenney wrote:
> N3201 Operator Overloading Without Name Mangling v2
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3201.pdf
> I have seen Linux-kernel interest in *function* overloading, but
> not in operator overloading. Nevertheless...
>
> The trick here is to associate a given operator with a function,
> so that the name-mangling becomes essentially a manual operation.
The proposal discusses strings, but I would want to immediately use this
for handling wrap vs trap arithmetic (rather than using sanitizers[1]).
--
Kees Cook
prev parent reply other threads:[~2024-01-23 22:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 16:46 A few proposals from the C standards committee Paul E. McKenney
2024-01-23 18:58 ` Linus Torvalds
2024-01-23 20:00 ` Paul E. McKenney
2024-01-23 20:20 ` Linus Torvalds
2024-01-23 20:35 ` Jakub Jelinek
2024-01-23 20:43 ` Linus Torvalds
2024-01-23 20:46 ` H. Peter Anvin
2024-01-24 13:46 ` Paul E. McKenney
2024-01-25 13:00 ` Paul E. McKenney
2024-01-24 13:16 ` Paul E. McKenney
2024-01-23 20:44 ` H. Peter Anvin
2024-01-24 12:52 ` Paul E. McKenney
2024-01-23 20:39 ` Linus Torvalds
2024-01-23 22:35 ` Martin Uecker
2024-01-23 20:16 ` H. Peter Anvin
2024-01-23 20:24 ` Linus Torvalds
2024-01-24 14:58 ` Paul E. McKenney
2024-01-25 12:52 ` Paul E. McKenney
2024-01-23 22:39 ` Kees Cook [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=202401231437.171F50B769@keescook \
--to=keescook@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=justinstitt@google.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).