https://issues.dlang.org/show_bug.cgi?id=10661

David Nadlinger <code@klickverbot.at> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |code@klickverbot.at

--- Comment #1 from David Nadlinger <code@klickverbot.at> ---
+1, this is essential for resilient crypto code.

--

https://issues.dlang.org/show_bug.cgi?id=10661

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugzilla@digitalmars.com

--- Comment #2 from Walter Bright <bugzilla@digitalmars.com> ---
So who wants to implement it?

--

https://issues.dlang.org/show_bug.cgi?id=10661

--- Comment #3 from bearophile_hugs@eml.cc ---
(In reply to Walter Bright from comment #2)
> So who wants to implement it?

How do you like to implement it? As a special case, or introducing some kind of generic and reusable annotation, like @keep_function that tells the D compiler to never optimize away the calls to a specific function? I don't know what other cases there are of functions that must never be removed.

--

https://issues.dlang.org/show_bug.cgi?id=10661

yebblies <yebblies@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yebblies@gmail.com

--- Comment #4 from yebblies <yebblies@gmail.com> ---
(In reply to bearophile_hugs from comment #3)
> (In reply to Walter Bright from comment #2)
> > So who wants to implement it?
> 
> How do you like to implement it? As a special case, or introducing some kind of generic and reusable annotation, like @keep_function that tells the D compiler to never optimize away the calls to a specific function? I don't know what other cases there are of functions that must never be removed.

volatileMemset

--

https://issues.dlang.org/show_bug.cgi?id=10661

--- Comment #5 from Walter Bright <bugzilla@digitalmars.com> ---
volatileMemset() should call the C memset_s() function, if that function
exists.

Also, there should be a zeroRegisters() function that zeros out all the scratch
registers.

--

https://issues.dlang.org/show_bug.cgi?id=10661

--- Comment #6 from Orvid King <blah38621@gmail.com> ---
I believe this should be in the runtime rather than phobos, primarily because it is very dependent on the specific architecture in use.

--

https://issues.dlang.org/show_bug.cgi?id=10661

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P4

--