Related articles |
---|
Crypto friendly optimization? johnl@taugh.com (John R Levine) (2024-08-24) |
Re: Crypto friendly optimization? Keith.S.Thompson+u@gmail.com (Keith Thompson) (2024-08-24) |
Re: Crypto friendly optimization? ianlancetaylor@gmail.com (Ian Lance Taylor) (2024-08-24) |
Re: Crypto friendly optimization? Keith.S.Thompson+u@gmail.com (Keith Thompson) (2024-08-24) |
Re: Crypto friendly optimization? david.brown@hesbynett.no (David Brown) (2024-08-25) |
Re: Crypto friendly optimization? anton@mips.complang.tuwien.ac.at (2024-08-25) |
Re: Crypto friendly optimization? david.brown@hesbynett.no (David Brown) (2024-08-25) |
Re: Crypto friendly optimization? pkk@spth.de (Philipp Klaus Krause) (2025-04-05) |
From: | Philipp Klaus Krause <pkk@spth.de> |
Newsgroups: | comp.compilers |
Date: | Sat, 05 Apr 2025 19:50:48 +0200 |
Organization: | Compilers Central |
References: | 24-08-003 24-08-004 24-08-008 |
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 |
In-Reply-To: | 24-08-008 |
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
Return to the
comp.compilers page.
Search the
comp.compilers archives again.