<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello Eric,</p>
<blockquote
cite="mid:CALehDX4oJZZ9=GzrAJx466qjsQwv1GGPbYsaW4VtBAkKb3yJ4w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>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>
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?<br>
<blockquote
cite="mid:CALehDX4oJZZ9=GzrAJx466qjsQwv1GGPbYsaW4VtBAkKb3yJ4w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>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>
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).
<blockquote
cite="mid:CALehDX4oJZZ9=GzrAJx466qjsQwv1GGPbYsaW4VtBAkKb3yJ4w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>-eric</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Fri, Feb 17, 2017 at 6:00 AM Victor Leschuk
via llvm-dev <<a moz-do-not-send="true"
href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" 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 moz-do-not-send="true"
href="mailto:llvm-dev@lists.llvm.org" class="gmail_msg"
target="_blank">llvm-dev@lists.llvm.org</a><br
class="gmail_msg">
<a moz-do-not-send="true"
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>
<pre class="moz-signature" cols="72">--
Best Regards,
Victor</pre>
</body>
</html>