Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.iecc.com!.POSTED.news.iecc.com!nerds-end
From: Philipp Klaus Krause <pkk@spth.de>
Newsgroups: comp.compilers
Subject: Re: Crypto friendly optimization?
Date: Sat, 05 Apr 2025 19:50:48 +0200
Organization: Compilers Central
Sender: johnl%iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <25-04-001@comp.compilers>
References: <24-08-003@comp.compilers> <24-08-004@comp.compilers> <24-08-008@comp.compilers>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="48796"; mail-complaints-to="abuse@iecc.com"
Keywords: optimize
Posted-Date: 05 Apr 2025 14:20:06 EDT
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
In-Reply-To: <24-08-008@comp.compilers>
Xref: csiph.com comp.compilers:3640

Am 25.08.24 um 18:06 schrieb anton@mips.complang.tuwien.ac.at:
>> I'm not aware of any current implementations that support it.
>
> That's trivial:
>
> void *memset_explicit( void *dest, int ch, size_t count )
> {
>    memset(dest, ch, count);
> }

SDCC has had memset_explicit since SDCC 4.2.0 (released 2021), and this
is the implementation:

#include <string.h>

void *memset_explicit (void *s, int c, size_t n)
{
   return(memset(s, c, n));
}

Since SDCC does not have link-time optimization, and the implementation
resides in its own source file by itself, this is sufficient to ensure
that it does not get optimized out.

Philipp