Displaying 6 results from an estimated 6 matches for "heyimacxxfunction".
2011 Nov 25
5
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...cxx-abi -Xclang microsoft
; ModuleID = 'mangling.cpp'
target datalayout =
"e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-f80:128:128-v64:64:64-
v128:128:128-a0:0:64-f80:32:32-n8:16:32-S32"
target triple = "i686-pc-win32"
define i32 @"?heyimacxxfunction@@YAHXZ"() nounwind readnone {
entry:
ret i32 42
}
Note the ?heyimacxxfunction@@YAHXZ. Now if I generate assembly (using
clang or llc) I get:
$ clang++ -S -O3 mangling.cpp -o - -Xclang -cxx-abi -Xclang microsoft
.def __3F_heyimacxxfunction@@YAHXZ;
.scl 2;
.typ...
2011 Nov 25
2
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...pp'
>> target datalayout =
>> "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-f80:128:128-v64:64:64-
>> v128:128:128-a0:0:64-f80:32:32-n8:16:32-S32"
>> target triple = "i686-pc-win32"
>>
>> define i32 @"?heyimacxxfunction@@YAHXZ"() nounwind readnone {
>> entry:
>> ret i32 42
>> }
>>
>> Note the ?heyimacxxfunction@@YAHXZ. Now if I generate assembly (using
>> clang or llc) I get:
>>
>> $ clang++ -S -O3 mangling.cpp -o - -Xclang -cxx-abi -Xclang microsoft
>>...
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...duleID = 'mangling.cpp'
> target datalayout =
> "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-f80:128:128-v64:64:64-
> v128:128:128-a0:0:64-f80:32:32-n8:16:32-S32"
> target triple = "i686-pc-win32"
>
> define i32 @"?heyimacxxfunction@@YAHXZ"() nounwind readnone {
> entry:
> ret i32 42
> }
>
> Note the ?heyimacxxfunction@@YAHXZ. Now if I generate assembly (using
> clang or llc) I get:
>
> $ clang++ -S -O3 mangling.cpp -o - -Xclang -cxx-abi -Xclang microsoft
> .def __3F_heyimacxxfunct...
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...get datalayout =
>>> "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-f80:128:128-v64:64:64-
>>> v128:128:128-a0:0:64-f80:32:32-n8:16:32-S32"
>>> target triple = "i686-pc-win32"
>>>
>>> define i32 @"?heyimacxxfunction@@YAHXZ"() nounwind readnone {
>>> entry:
>>> ret i32 42
>>> }
>>>
>>> Note the ?heyimacxxfunction@@YAHXZ. Now if I generate assembly (using
>>> clang or llc) I get:
>>>
>>> $ clang++ -S -O3 mangling.cpp -o - -Xclang -cxx...
2011 Nov 26
1
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...t;>>> "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-f80:128:128-v64:64:64-
>>>> v128:128:128-a0:0:64-f80:32:32-n8:16:32-S32"
>>>> target triple = "i686-pc-win32"
>>>>
>>>> define i32 @"?heyimacxxfunction@@YAHXZ"() nounwind readnone {
>>>> entry:
>>>> ret i32 42
>>>> }
>>>>
>>>> Note the ?heyimacxxfunction@@YAHXZ. Now if I generate assembly (using
>>>> clang or llc) I get:
>>>>
>>>> $ clang++ -S -O3...
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...duleID = 'mangling.cpp'
> target datalayout =
> "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-f80:128:128-v64:64:64-
> v128:128:128-a0:0:64-f80:32:32-n8:16:32-S32"
> target triple = "i686-pc-win32"
>
> define i32 @"?heyimacxxfunction@@YAHXZ"() nounwind readnone {
> entry:
> ret i32 42
> }
>
> Note the ?heyimacxxfunction@@YAHXZ. Now if I generate assembly (using
> clang or llc) I get:
>
> $ clang++ -S -O3 mangling.cpp -o - -Xclang -cxx-abi -Xclang microsoft
> .def __3F_heyimacxxfunct...