lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <202401231437.171F50B769@keescook>
Date: Tue, 23 Jan 2024 14:39:58 -0800
From: Kees Cook <keescook@...omium.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: linux-toolchains@...r.kernel.org, peterz@...radead.org, hpa@...or.com,
	rostedt@...dmis.org, gregkh@...uxfoundation.org,
	ndesaulniers@...gle.com, justinstitt@...gle.com,
	torvalds@...ux-foundation.org, linux-hardening@...r.kernel.org
Subject: Re: A few proposals from the C standards committee

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ