> statically analyzing the assembly I must concede this notion troubles me now that you mentioned it, it is indeed possible that GCC or Clang could decide that

> statically analyzing the assembly I must concede this notion troubles me now that you mentioned it, it is indeed possible that GCC or Clang could decide that there is some other way explicit memset-like stuff should be done; and boringssl could deal with it, they are not a stable API for one thing, and Google employs GCC, LLVM and Clang developers anyway so it would be easier for BoringSSL than the rest of the world to fix the compilers changing stuff...