Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] gdb/dwarf: fix reading subprogram with DW_AT_specification (PR gdb/26693)
Date: Thu, 22 Oct 2020 08:18:43 -0600	[thread overview]
Message-ID: <87h7qmcpj0.fsf@tromey.com> (raw)
In-Reply-To: <ed370dc5-8afe-7403-7253-2957bbd63c40@polymtl.ca> (Simon Marchi's message of "Wed, 21 Oct 2020 22:37:07 -0400")

>> gdb currently goes through a lot of work to support DWARF like this, but
>> I wish it didn't have to.  It complicates the DWARF reader -- but IIRC
>> both gcc and clang just emit specializations with names like
>> "apply<int>".  So, I wonder if we could drop support for this at some
>> point.

Simon> The object that contained this kind of DWARF, that made GDB crash, was
Simon> compiled with ICC.  So unless we decide to drop support for ICC, I don't
Simon> think we can get rid of it any time soon.

Well, we could support it in a more limited way - like, these functions
would still appear but without template parameters in their names.

We could try to get a clarification from DWARF as to whether icc or
gcc/clang are correct here, then file bug(s) against the compiler.

Simon> I would write this, does that sound good?

Simon> /* Load the DIEs associated with PER_CU into memory.

Simon>    In some cases, the caller, while reading partial symbols, will need to load
Simon>    the full symbols for the CU for some reason.  It will already have a
Simon>    dwarf2_cu object for THIS_CU and pass it as EXISTING_CU, so it can be re-used
Simon>    rather than creating a new one.  */

Looks great, thank you.

Tom

  reply	other threads:[~2020-10-22 14:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 14:18 [PATCH] " Simon Marchi via Gdb-patches
2020-10-20 15:13 ` Simon Marchi via Gdb-patches
2020-10-20 15:55   ` Strasuns, Mihails via Gdb-patches
2020-10-20 16:29   ` Tom de Vries
2020-10-20 16:48     ` Simon Marchi via Gdb-patches
2020-10-20 16:50       ` [PATCH v2] " Simon Marchi via Gdb-patches
2020-10-21 20:42         ` Tom Tromey
2020-10-22  2:37           ` Simon Marchi via Gdb-patches
2020-10-22 14:18             ` Tom Tromey [this message]
2020-10-22 14:51               ` Simon Marchi via Gdb-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7qmcpj0.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox