Home
last modified time | relevance | path

Searched refs:ODR (Results 1 – 15 of 15) sorted by relevance

/external/swiftshader/third_party/LLVM/include/llvm/
DGlobalValue.h113 static LinkageTypes getLinkOnceLinkage(bool ODR) { in getLinkOnceLinkage() argument
114 return ODR ? LinkOnceODRLinkage : LinkOnceAnyLinkage; in getLinkOnceLinkage()
116 static LinkageTypes getWeakLinkage(bool ODR) { in getWeakLinkage() argument
117 return ODR ? WeakODRLinkage : WeakAnyLinkage; in getWeakLinkage()
/external/swiftshader/third_party/llvm-subzero/include/llvm/IR/
DGlobalValue.h256 static LinkageTypes getLinkOnceLinkage(bool ODR) { in getLinkOnceLinkage() argument
257 return ODR ? LinkOnceODRLinkage : LinkOnceAnyLinkage; in getLinkOnceLinkage()
259 static LinkageTypes getWeakLinkage(bool ODR) { in getWeakLinkage() argument
260 return ODR ? WeakODRLinkage : WeakAnyLinkage; in getWeakLinkage()
/external/llvm/include/llvm/IR/
DGlobalValue.h239 static LinkageTypes getLinkOnceLinkage(bool ODR) { in getLinkOnceLinkage() argument
240 return ODR ? LinkOnceODRLinkage : LinkOnceAnyLinkage; in getLinkOnceLinkage()
242 static LinkageTypes getWeakLinkage(bool ODR) { in getWeakLinkage() argument
243 return ODR ? WeakODRLinkage : WeakAnyLinkage; in getWeakLinkage()
/external/compiler-rt/lib/asan/
Dasan_flags.inc131 "If >=2, detect violation of One-Definition-Rule (ODR); "
132 "If ==1, detect ODR-violation only if the two variables "
141 "Use special ODR indicator symbol for ODR violation detection")
/external/clang/docs/
DLTOVisibility.rst19 ODR violation to define a class with hidden LTO visibility in multiple linkage
23 visibility. A class's LTO visibility is treated as an ODR-relevant property
48 visibility in order to avoid an ODR violation.
103 an ODR violation.
/external/skia/src/opts/
DSkOpts_avx.cpp12 #error We have included ucrt\math.h without protecting it against ODR violation.
/external/llvm/test/ThinLTO/X86/
Dweak_resolution.ll7 ; non-prevailing ODR are not kept when possible, but non-ODR non-prevailing
Dalias_resolution.ll7 ; There is no importing going on with this IR, but let's check the ODR resolution for compile time
/external/llvm/test/Linker/
Dtype-unique-odr-b.ll4 ; Test ODR-based type uniquing for C++ class members.
Dtype-unique-odr-a.ll12 ; Test ODR-based type uniquing for C++ class members.
/external/llvm/test/DebugInfo/Generic/
Dcross-cu-linkonce-distinct.ll6 ; still fulfilling C++'s ODR by having identical token sequences) functions,
/external/llvm/test/DebugInfo/COFF/
Dtypes-recursive-struct.ll7 ; streams even if the complete record types differ slightly due to ODR
/external/libcxx/
DCMakeLists.txt445 # the dylib when get ODR used by another function.
/external/clang/include/clang/Basic/
DAttrDocs.td210 whether a C++ template specialization is ODR-equivalent), but is not part of
241 share ODR-equivalent enable_if expressions, the overload resolution is
256 expression is ODR-equivalent for both declarations, but #1 does not have another
260 not ODR-equivalent.
/external/llvm/docs/
DLangRef.rst266 "one definition rule" --- "ODR"). Such languages can use the
4057 ``offset:`` is the member's bit offset. If the composite type has an ODR
4081 If the source language supports ODR, the ``identifier:`` field gives the unique
4084 derived types <DIDerivedTypeMember>` that reference the ODR-type in their
4218 type with an ODR ``identifier:`` and that does not set ``flags: DIFwdDecl``,