From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <musl-return-20667-ml=inbox.vuxu.org@lists.openwall.com>
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4
Received: from second.openwall.net (second.openwall.net [193.110.157.125])
	by inbox.vuxu.org (Postfix) with SMTP id 390B425E17
	for <ml@inbox.vuxu.org>; Tue, 19 Mar 2024 17:37:39 +0100 (CET)
Received: (qmail 29840 invoked by uid 550); 19 Mar 2024 16:33:08 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 29802 invoked from network); 19 Mar 2024 16:33:07 -0000
X-Virus-Scanned: SPAM Filter at disroot.org
Date: Tue, 19 Mar 2024 16:37:21 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail;
	t=1710866245; bh=zn7jmfsqQ++Wheo5bQ9lf7XgJ59BE8nRYnry8BNwy7E=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To;
	b=hJha1sR8qIAuPo5LNT+LFZ8RgYe7xQCFcp3XpfdqEdz9bSN+J/Ou6cXbRVRz/+biv
	 SspJx/tUv1Uy5PpYcFbNQe9GNWp+UhM9TpqsmhVCQ9FQZfv6S4HkA+kPdBojagoAWZ
	 s8k2jTqlUPSD87vgG1n/znYSvq60YxMUFK1nEllRTso7Hku/+EQP0zskJTVlkNAPh3
	 YWFDhbuQs/dxaGZmWLKIIM9i1TLCIPsA8LUTQZYuxcDep5sQCk5ZtEKLq3ZZobo3vU
	 doGdlmWlxR4J1lsc5ynnHTCuhl5RKl8PxxoMfVVyPaPBw9JzkhyD/fZnMM/1RanJAi
	 Il0JGMP9/t0HA==
From: NRK <nrk@disroot.org>
To: musl@lists.openwall.com
Cc: =?utf-8?B?SuKCkeKCmeKCmw==?= Gustedt <jens.gustedt@inria.fr>, 
	Aaron Peter Bachmann <aaron_ng@inode.at>
Message-ID: <fxg6zacf3cvsjklt5rha6ty2qbxvthwuo352dxtzlmo4upqumu@42j5ziybhe6p>
References: <1ad1a194-f2f5-4ae1-9686-67961086e605@inode.at>
 <20240319145026.34c1a068@inria.fr>
 <20240319140213.GJ4163@brightrain.aerifal.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20240319140213.GJ4163@brightrain.aerifal.cx>
Subject: Re: [musl] c23 memset_explicit()

> I'm not sure what the builtin thing was.

IIRC, the idea was that if memset_explicit() is recognized by compilers
then they can make better decision. E.g if the data is held in a
register without any further copy in memory, then compiler can just
clear the register instead of spilling it onto the stack and calling
memset_explicit() on it.

But that's not really relevant for libcs trying to add support for it.
Both of them can co-exist.

- NRK