[llvm] r192018 - Debug Info: In DIBuilder, the derived-from field of a DW_TAG_pointer_type

[Eric Christopher]

>>
>> Also we might want to just make this a method on DwarfDebug since it
>> has the information to connect the various references.
>
>
> We have a few static helper functions: isTypeSigned, getBaseTypeSize, and
> isUnsignedDIType.
> isTypeUnitScoped traces along the context chain while the above three traces
> along the derived-from chain.
> Should we make all four member functions then? DwarfDebug or CompileUnit?
>

Basically if you're passing in a DwarfDebug anyways then making it a
member function is losing you anything.

And how about DwarfDebug for now unless they need to access anything
in the compile unit as well.

-eric