Searched refs:mangling (Results 1 – 25 of 128) sorted by relevance
123456
11 * name mangling that matches the API prefixing that happened as a result of12 * --with-mangling and/or --with-jemalloc-prefix configuration settings.32 * provide isolation from the name mangling specified via --with-mangling
7 * Name mangling for public symbols is controlled by --with-mangling and
1 // RUN: %clang_cc1 %s -ffake-address-space-map -faddress-space-map-mangling=yes -triple %itanium_ab…2 // RUN: %clang_cc1 %s -cl-std=CL2.0 -ffake-address-space-map -faddress-space-map-mangling=yes -trip…3 // RUN: %clang_cc1 %s -ffake-address-space-map -faddress-space-map-mangling=no -triple %itanium_abi…4 // RUN: %clang_cc1 %s -cl-std=CL2.0 -ffake-address-space-map -faddress-space-map-mangling=no -tripl…
25 // because the OCL specification on the Itanium ABI has a specified mangling27 // into account. Thus, both would result in the same mangling, which is an IR-CodeGen28 // error. Our windows implementation of this mangling doesn't have that problem,
1 // RUN: %clang_cc1 %s -ffake-address-space-map -faddress-space-map-mangling=no -triple %itanium_abi…
274 let mut mangling = cursor.mangling(); in cursor_mangling() localVariable275 if mangling.is_empty() { in cursor_mangling()299 if mangling.ends_with("D0Ev") { in cursor_mangling()300 let new_len = mangling.len() - 4; in cursor_mangling()301 mangling.truncate(new_len); in cursor_mangling()302 mangling.push_str("D1Ev"); in cursor_mangling()306 Some(mangling) in cursor_mangling()
1 // RUN: %clang_cc1 %s -ffake-address-space-map -faddress-space-map-mangling=yes -triple %itanium_ab…2 // RUN: %clang_cc1 %s -ffake-address-space-map -faddress-space-map-mangling=no -triple %itanium_abi…
42 // The map key is a mangling of the containing function and op name with49 // It would be preferable to avoid mangling and use a tuple key of (op.name,
3 ; CHECK: Expected mangling specifier in datalayout string
3 ; CHECK: Unknown mangling in datalayout string
3 ; CHECK: Unexpected trailing characters after mangling specifier in datalayout string
35 Compile errors with --enable-mangling89 - glx: Fix build errors with --enable-mangling (v2)
3 ; Tests the name mangling performed by the codepath following5 ; run fine: doesn't actually test the mangling with the type of the
6 // get the same unqualified-block mangling because the logic to handle
13 Manage name mangling (prefixing with '_') manually because 'PREFIX' does not
13 ; Check that a fastcall function gets correct mangling
7 # _bar_std@8, and then exports _foo_std@8. Same for fastcall and other mangling
6 ; type will fail because llvm does not support mangling vector of pointers.