search for: printf_chk

...y propagation. With that pointer assignment there, GCC sees it as a global aliasing the same memory location as the array, and that global escapes the function. Because of that, it no longer believes it knows what happens to the memory once the printf call happens (since it's really a call to printf_chk, and because of the way glibc works, printf is not a readonly functiojn) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140812/ac536597/attachment.html>