<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p> </p>
<div style="FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px">
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>
<div style="FONT-FAMILY: Tahoma; DIRECTION: ltr; FONT-SIZE: 10pt">
<div style="FONT-FAMILY: Times New Roman; FONT-SIZE: 16px">
<div>
<div dir="ltr">
<div>This is in enum llvm_dwarf_constants, not enum dwarf_constants.</div>
<div>It's one of several mock tags defined for the metadata interface;</div>
<div>they are not defined by DWARF. (If the number of real DWARF tags</div>
<div>doubles, we'll have to renumber these to get out of the way.)</div>
<div>
<div> </div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>> Yeah, we're looking at getting rid of those, I'm not sure it's needed ... (more at the end)</div>
<div> </div>
<div>
<div>I made a new subclass for static members because normal members currently use DIDerivedType and there are already snippy remarks in the commentary about what a hack that is (there's at least one extra field in DIDerivedType that's used only for members).
AFAICT the subclasses have to be distinguishable by tag, so I invented a new tag.</div>
<div> </div>
<div>If a future patch migrates normal members onto the new subclass, and there's some other way to distinguish normal and static members within that subclass (e.g. a new flag), then the new subclass can be identified using DW_TAG_member (which would no longer
be valid for DIDerivedType) and we can get rid of DW_TAG_CXX_static_member.</div>
<div>--paulr</div>
<div> </div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>