search for: _zn1a

Displaying 4 results from an estimated 4 matches for "_zn1a".

Did you mean: _zbs1a
2014 Jul 09
4
[LLVMdev] Issues with clang-llvm debug info validity
...e to DIScope::getRef() >>>> - Let CGDebugInfo create a mangled name for each namespace to use as UID >>>> -> the UID of the anonymous namespace is null. >>>> >>>> For example: >>>> >>>> namespace a { namespace b {} } -> “_ZN1a", “_ZN1a1b" >>>> >>>> !0 = [compile unit] >>>> !1 = metadata !{i32 786489, metadata !0, metadata !”_ZN1a", metadata !”b", i32 1, metadata !”_ZN1a1b"} ; [ DW_TAG_namespace ] [a] >>>> !2 = metadata !{i32 786489, metadata !0, nul...
2014 Jun 27
2
[LLVMdev] Issues with clang-llvm debug info validity
...- extend DINamespace with an extra UniqueID filed (analogous to DICompositeType) - add an extra case to DIScope::getRef() - Let CGDebugInfo create a mangled name for each namespace to use as UID -> the UID of the anonymous namespace is null. For example: namespace a { namespace b {} } -> “_ZN1a", “_ZN1a1b" !0 = [compile unit] !1 = metadata !{i32 786489, metadata !0, metadata !”_ZN1a", metadata !”b", i32 1, metadata !”_ZN1a1b"} ; [ DW_TAG_namespace ] [a] !2 = metadata !{i32 786489, metadata !0, null, metadata !”a", i32 1, metadata !”_ZN1a"} ; [ DW_TAG_na...
2014 Jun 27
2
[LLVMdev] Issues with clang-llvm debug info validity
...o DICompositeType) >> - add an extra case to DIScope::getRef() >> - Let CGDebugInfo create a mangled name for each namespace to use as UID >> -> the UID of the anonymous namespace is null. >> >> For example: >> >> namespace a { namespace b {} } -> “_ZN1a", “_ZN1a1b" >> >> !0 = [compile unit] >> !1 = metadata !{i32 786489, metadata !0, metadata !”_ZN1a", metadata !”b", i32 1, metadata !”_ZN1a1b"} ; [ DW_TAG_namespace ] [a] >> !2 = metadata !{i32 786489, metadata !0, null, metadata !”a", i32 1, m...
2014 Jun 24
2
[LLVMdev] Issues with clang-llvm debug info validity
>> Without needing to change how namespaces are handled. >> >> Yes, using DIRefs for namespaces would cause the actual type nodes to >> be deduplicated when they aren't even with the patch above, and that >> would help reduce debug info metadata further if that's >> useful/necessary. > > Exactly. While the above patch will cover up the problem, we