Displaying 3 results from an estimated 3 matches for "01_foo".
Did you mean:
00foo
2012 Mar 13
3
[LLVMdev] Your commit 103140
...label emitted multiple times to assembly}
> +target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:128:128-n8:16:32"
> +target triple = "i386-apple-darwin10.0.0"
> +
> +define i32 @"\01_foo"() {
> + unreachable
> +}
> +
> +define i32 @foo() {
> +entry:
> + unreachable
> +}
> +
> +declare i32 @xstat64(i32, i8*, i8*)
> Index: lib/CodeGen/AsmPrinter/AsmPrinter.cpp
> ===================================================================
> --- lib/Co...
2012 Mar 13
0
[LLVMdev] Your commit 103140
...asm renaming and USER_LABEL_PREFIX), I think it is best for the frontend to not use the "\01" prefix in a case that conflicts with the normal USER_LABEL_PREFIX. For example, on an _'y system, if asm-renamed to "_foo", the IR name should be just @"foo", not "\01_foo".
I think I agree. My agreement is helped by noticing that the assembler produced
by gcc for the testcase from PR397 doesn't assemble! One of my side worries was
that the MC layer wouldn't be able to assemble the assembler produced by gcc if
it contained multiple functions with the...
2012 Mar 13
0
[LLVMdev] Your commit 103140
...asm renaming and USER_LABEL_PREFIX), I think it is best for the frontend to not use the "\01" prefix in a case that conflicts with the normal USER_LABEL_PREFIX. For example, on an _'y system, if asm-renamed to "_foo", the IR name should be just @"foo", not "\01_foo".
-Chris