Home
last modified time | relevance | path

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

/freebsd-14.2/contrib/llvm-project/llvm/include/llvm/IR/
H A DGlobalValue.h368 static LinkageTypes getLinkOnceLinkage(bool ODR) { in getLinkOnceLinkage() argument
369 return ODR ? LinkOnceODRLinkage : LinkOnceAnyLinkage; in getLinkOnceLinkage()
371 static LinkageTypes getWeakLinkage(bool ODR) { in getWeakLinkage() argument
372 return ODR ? WeakODRLinkage : WeakAnyLinkage; in getWeakLinkage()
/freebsd-14.2/contrib/llvm-project/clang/include/clang/Basic/
H A DDiagnosticASTKinds.td457 InGroup<ODR>;
462 InGroup<ODR>;
470 InGroup<ODR>;
497 InGroup<ODR>;
506 InGroup<ODR>;
511 InGroup<ODR>;
520 InGroup<ODR>;
527 InGroup<ODR>;
534 InGroup<ODR>;
541 InGroup<ODR>;
[all …]
H A DCodeGenOptions.def243 CODEGENOPT(SanitizeAddressUseOdrIndicator, 1, 0) ///< Enable ODR indicator globals
H A DLangOptions.def177 LANGOPT(SkipODRCheckInGMF, 1, 0, "Skip ODR checks for decls in the global module fragment")
H A DDiagnosticGroups.td21 def ODR : DiagGroup<"odr">;
H A DAttrDocs.td813 whether a C++ template specialization is ODR-equivalent), but is not part of
844 share ODR-equivalent enable_if expressions, the overload resolution is
859 expression is ODR-equivalent for both declarations, but #1 does not have another
863 not ODR-equivalent.
/freebsd-14.2/contrib/llvm-project/llvm/tools/llvm-dwarfutil/
H A DOptions.td29 "Do ODR deduplication for debug types(default)",
30 "Don`t do ODR deduplication for debug types">;
/freebsd-14.2/sys/contrib/device-tree/Bindings/ipmi/
H A Daspeed-kcs-bmc.txt21 - reg : The address and size of the IDR, ODR and STR registers
H A Daspeed,ast2400-kcs-bmc.yaml40 - description: ODR register
/freebsd-14.2/contrib/llvm-project/lld/docs/ELF/
H A Dwarn_backrefs.rst98 In C++, this is likely an ODR violation. We probably need a dedicated option
99 for ODR detection.
/freebsd-14.2/contrib/llvm-project/compiler-rt/lib/asan/
H A Dasan_flags.inc151 "If >=2, detect violation of One-Definition-Rule (ODR); "
152 "If ==1, detect ODR-violation only if the two variables "
/freebsd-14.2/contrib/llvm-project/lld/docs/MachO/
H A Dld64-vs-lld.rst11 the opposite. ld64's behavior hides ODR violations, so we have chosen not
/freebsd-14.2/sys/contrib/device-tree/Bindings/pinctrl/
H A Dpinctrl-mcp23s08.txt50 - drive-open-drain: Sets the ODR flag in the IOCON register. This configures
/freebsd-14.2/contrib/llvm-project/libcxx/include/
H A D__config818 // 2. The symbol is given an ABI tag that encodes the ODR-relevant properties of the library.
819 // This ensures that no ODR violation can arise from mixing two TUs compiled with different
821 // program contains two definitions of a function, the ODR requires them to be token-by-token
828 // and the other aborts the program). This violates the ODR and makes the program ill-formed, an…
832 // A similar reasoning holds for many other properties that are ODR-affecting. Essentially any
834 // can be considered ODR-affecting. In practice, we don't encode all such properties in the ABI
/freebsd-14.2/contrib/llvm-project/clang/include/clang/AST/
H A DCXXRecordDeclDefinitionBits.def28 /// NO_MERGE: It is an ODR violation if the fields do not match.
/freebsd-14.2/contrib/llvm-project/clang/include/clang/Driver/
H A DOptions.td2340 PosFlag<SetTrue, [], [ClangOption], "Enable ODR indicator globals to avoid false ODR violation"
2342 NegFlag<SetFalse, [], [ClangOption], "Disable ODR indicator globals">>,
2991 "Skip ODR checks for decls in the global module fragment.">,
2993 "Perform ODR checks for decls in the global module fragment.">>,