[LLVMdev] Handling of unsafe functions

Florian Weimer fweimer at redhat.com
Thu Nov 29 05:33:02 PST 2012

On 10/03/2012 08:30 AM, Martinez, Javier E wrote:

> I've modified the original proposal to strike the middle of the road. Instead of only providing a 4-parameter version of memcpy_secure now a 3-parameter version also exists. The latter maps to memcpy or memcpy_s depending on what's available as determined by the CMake scripts. The 4-parameter version replaces those calls to memcpy where safe use can't be determined. All other calls will be replaced to the 3-parameter version.

Sorry, but I think this change only makes understanding of the code more 

Florian Weimer / Red Hat Product Security Team

More information about the llvm-dev mailing list