search for: string_00000001

...didn't call free. This is related to http://llvm.org/PR8908#c1 .) One other thing we may want is a flag for "does not care about the pointer itself, only what the pointer points to". Currently, nothing tells LLVM that puts() doesn't check whether the pointer argument == &string_00000001, so we can't actually remove the copy. We could special-case that optimization into SimplifyLibCalls. Nick

Hello, I'm developing a programming language that is optimized for strings. A first hello world program shows me that llvm needs a lot more work on zero terminated strings. In the following example, I have an auto generated hello world example optimized with -O3. The problem is, that the constant string is copied into a malloced mem area, then puts is called and then the memory is freed.