Re: crypto_memset (was: Re: Zero it if you're going to copy it out.)

["Aaron J. Grier" <agrier%poofygoof.com@localhost>]

On Tue, Aug 28, 2012 at 09:58:07PM +0200, Alan Barrett wrote:
> I prefer to rely on the definition of volatile pointers, rather than
> relying on the compiler to be unable to optimise across compilation
> unit boundaries.  Code gets cut and pasted, so the definition of
> explicit_bzero might end up in the same compilation unit as its
> caller.

shouldn't you be relying on explicit memory barriers instead of volatile
pointers?  

-- 
  Aaron J. Grier | "Not your ordinary poofy goof." | 
agrier%poofygoof.com@localhost