Philipp Klaus Krause wrote:
> Am 11.08.20 um 02:48 schrieb Damien Miller:
> >
> > We went with explict_bzero because our only use-case for this was
> > safe erasure that could not be elided by the compiler.
> >
> > I don't see any need for explicit_memset() - if anything depends on
> > the over
Am 11.08.20 um 02:48 schrieb Damien Miller:
>
> We went with explict_bzero because our only use-case for this was
> safe erasure that could not be elided by the compiler.
>
> I don't see any need for explicit_memset() - if anything depends on
> the overwritten value then simple memset() should be
On Mon, 10 Aug 2020, Amit Kulkarni wrote:
> moving to tech@
>
> -- Forwarded message -
> From: Philipp Klaus Krause
> Date: Mon, Aug 10, 2020 at 4:34 AM
> Subject: explicit_bzero vs. alternatives
> To:
>
>
> OpenBSD has the explicit_bzero func
>
>
> OpenBSD has the explicit_bzero function to reliably (i.e. even if not
> observable in the C abstract machine) overwrite memory with zeroes.
> WG14 is currently considering adding similar functionality to C2X.
>
> Considered options include:
>
> * A function like explicit_bzero or memset_expli
moving to tech@
-- Forwarded message -
From: Philipp Klaus Krause
Date: Mon, Aug 10, 2020 at 4:34 AM
Subject: explicit_bzero vs. alternatives
To:
OpenBSD has the explicit_bzero function to reliably (i.e. even if not
observable in the C abstract machine) overwrite memory with
