search for: 01lstat64

Hi Chris, your commit 103140 broke PR397 for llvm-gcc (in LLVM 2.9) and dragonegg. In the PR, asm renaming creates two linkonce functions with the same asm name (in the IR they are @"\01lstat64" and "@lstat64". What used to happen is that they were both output to the assembler file, both with the name lstat64, exactly like GCC does. The assembler and linker are perfectly happy about this, presumably because the functions have weak linkage. What happens now is that compil...

...AM, Duncan Sands wrote: > >> Hi Chris, your commit 103140 broke PR397 for llvm-gcc (in LLVM 2.9) and >> dragonegg. > > Wow, this is an old patch :). > >> In the PR, asm renaming creates two linkonce functions with >> the same asm name (in the IR they are @"\01lstat64" and "@lstat64". What >> used to happen is that they were both output to the assembler file, both >> with the name lstat64, exactly like GCC does. The assembler and linker >> are perfectly happy about this, presumably because the functions have weak >> linka...

On Mar 13, 2012, at 8:26 AM, Duncan Sands wrote: > Hi Chris, your commit 103140 broke PR397 for llvm-gcc (in LLVM 2.9) and > dragonegg. Wow, this is an old patch :). > In the PR, asm renaming creates two linkonce functions with > the same asm name (in the IR they are @"\01lstat64" and "@lstat64". What > used to happen is that they were both output to the assembler file, both > with the name lstat64, exactly like GCC does. The assembler and linker > are perfectly happy about this, presumably because the functions have weak > linkage. What happen...