[LLVMdev] Handling of unsafe functions
Dmitri Gribenko
gribozavr at gmail.com
Mon Sep 24 14:14:20 PDT 2012
On Fri, Sep 21, 2012 at 6:52 AM, Martinez, Javier E
<javier.e.martinez at intel.com> wrote:
> From the responses it’s pretty clear that the preference is to avoid using C
> string functions altogether. I’ve attached at list of calls in Clang/LLVM.
> The EASY/MEDIUM/DIFFICULT tag is an estimate of the effort to replace the
> call based on the location of the source buffer. If there are no objections
> I’ll prepare a patch that replaces the string manipulation functions an
> appropriate string object.
Thank you for the list. Fixed the Clang non-platform specific bits in
r164554. Didn't dare to fix other occurrences in Clang because they
are #ifdefed for Windows and I don't have a Windows machine to test.
Dmitri
--
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/
More information about the llvm-dev
mailing list