Displaying 2 results from an estimated 2 matches for "mdderivedtype".
Did you mean:
diderivedtype
2015 Feb 20
6
[LLVMdev] Questions before moving the new debug info hierarchy into place
...nd I haven't even started on `make
check-clang` (I imagine that'll all be done by hand).)
There are two outstanding issues I'd like some feedback on.
Pretty-printing the flags
=========================
I've noticed the `flags:` field is *harder* to read in the new assembly:
!MDDerivedType(flags: 16384, ...)
than the pretty-printed comments in the old:
!{!"...\\0016384", ...} ; ... [public] [rvalue reference]
I don't want to regress here.
In `DIDescriptor`, the flags are described in an enum bitfield:
FlagAccessibility = 1 << 0 | 1 << 1,...
2015 Feb 20
2
[LLVMdev] Questions before moving the new debug info hierarchy into place
...clang` (I imagine that'll all be done by hand).)
>
> There are two outstanding issues I'd like some feedback on.
>
> Pretty-printing the flags
> =========================
>
> I've noticed the `flags:` field is *harder* to read in the new assembly:
>
> !MDDerivedType(flags: 16384, ...)
>
> than the pretty-printed comments in the old:
>
> !{!"...\\0016384", ...} ; ... [public] [rvalue reference]
>
> I don't want to regress here.
>
> In `DIDescriptor`, the flags are described in an enum bitfield:
>
> FlagAc...