Displaying 3 results from an estimated 3 matches for "pr397".
Did you mean:
pr3997
2012 Mar 13
3
[LLVMdev] Your commit 103140
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, exactl...
2012 Mar 13
0
[LLVMdev] Your commit 103140
Hi Chris,
On 13/03/12 21:11, Chris Lattner wrote:
>
> 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...
2012 Mar 13
0
[LLVMdev] Your commit 103140
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...