<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Feb 17, 2017 at 11:33 AM Victor Leschuk <<a href="mailto:vleschuk@accesssoftek.com">vleschuk@accesssoftek.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
<p class="gmail_msg">Hello Eric,</p></div><div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
<blockquote type="cite" class="gmail_msg">
<div dir="ltr" class="gmail_msg">
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">In my opinion all of accelerated access (pubnames,
pubtypes, all of the accelerator tables) should be optionally
emitted, including the new debug_names work. Basically we
should let users produce the type of table based on the
consumer of the data rather than anything else - and default
to nothing because the tables are, as you gathered, rather
consumer specific.</div>
</div>
</blockquote></div><div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
Currently clang produces .debug_pubnames and .debug_pubtypes when
invoked with -g3, there is no -gpubnames (pubtypes, etc) switch as
it is in gcc. Are you suggesting we use similar behavior as gcc, eg
do not emit accel tables even with -g3 and add special options like
-gpubnames and -gnames?</div><div bgcolor="#FFFFFF" text="#000000" class="gmail_msg"><br class="gmail_msg"></div></blockquote><div><br></div><div>Yes. Exactly. There's already a ggnu-pubnames option which will produce pubnames that match the gcc version used with gold for gdb_index.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
<blockquote type="cite" class="gmail_msg">
<div dir="ltr" class="gmail_msg">
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">Right now, as far as I know, no debugger implements the
version of debug_names recently standardized so there's an
additional point to avoid using it for now.</div>
</div>
</blockquote></div><div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
GNU readelf has support for .debug_names (not merged to master yet,
but will be soon) and gdb is on its way (I am in touch with
binutils-gdb developer on this).</div></blockquote><div><br></div><div>Nifty. None of our tools do in the clang side, including emitting them.</div><div><br></div><div>-eric</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
</div><div bgcolor="#FFFFFF" text="#000000" class="gmail_msg"><blockquote type="cite" class="gmail_msg">
<div dir="ltr" class="gmail_msg">
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">-eric</div>
<br class="gmail_msg">
<div class="gmail_quote gmail_msg">
<div dir="ltr" class="gmail_msg">On Fri, Feb 17, 2017 at 6:00 AM Victor Leschuk
via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="gmail_msg" target="_blank">llvm-dev@lists.llvm.org</a>>
wrote:<br class="gmail_msg">
</div>
<blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all,<br class="gmail_msg">
<br class="gmail_msg">
I am implementing support for .debug_names section (which is
introduced<br class="gmail_msg">
in DWARFv5 standard as replacement for .debug_pubnames and<br class="gmail_msg">
.debug_pubtypes). The question is: should usage of DWARF
version 5 force<br class="gmail_msg">
generation of .debug_names instead of .debug_pubnames or we
can make it<br class="gmail_msg">
just default behavior and provide user with the interface
(cmd switch)<br class="gmail_msg">
to use other DWARFv5 features but generate old
.debug_pubnames and<br class="gmail_msg">
.debug_pubtypes? The thing is that there can be potential
DWARF consumer<br class="gmail_msg">
which doesn't fully support new standard. When we are
talking about<br class="gmail_msg">
attributes, etc it will just cause warnings, but unknown
section is much<br class="gmail_msg">
more serious issue.<br class="gmail_msg">
<br class="gmail_msg">
--<br class="gmail_msg">
Best Regards,<br class="gmail_msg">
Victor<br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
LLVM Developers mailing list<br class="gmail_msg">
<a href="mailto:llvm-dev@lists.llvm.org" class="gmail_msg" target="_blank">llvm-dev@lists.llvm.org</a><br class="gmail_msg">
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class="gmail_msg">
</blockquote>
</div>
</div>
</blockquote>
<br class="gmail_msg">
</div><div bgcolor="#FFFFFF" text="#000000" class="gmail_msg"><pre class="m_5169835621544184370moz-signature gmail_msg" cols="72">--
Best Regards,
Victor</pre>
</div></blockquote></div></div>