From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: Keith Seitz <keiths@redhat.com>, Tom Tromey <tom@tromey.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
"Metzger, Markus T" <markus.t.metzger@intel.com>
Subject: RE: Infcall of a template function in a C++ program
Date: Tue, 23 Jul 2019 16:24:00 -0000 [thread overview]
Message-ID: <B98F7326B8E238409968F562D326E1A90D04ACBD@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <defe4f64-ab65-2693-c7eb-ceed6128c114@redhat.com>
* On Tuesday, July 23, 2019 4:51 PM, Keith Seitz wrote:
>
> On 7/19/19 1:12 PM, Tom Tromey wrote:
> >
> > The "compile" command might also be promising here, though I don't know
> > how well the C++ support handles templates. It's a difficult problem
> > given the way the "compile" command was designed, because the source
> > isn't available and DWARF doesn't represent templates, only
> > instantiations.
>
> For the record: the upstream C++ compile feature does not include any template
> support at all. I do have some patches to start this process, but it
> is stalled on a number of outstanding issues (unresolved bugs, unreviewed
> patch(es?), etc).
>
> Keith
Are these patches available in some accessible branch?
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2019-07-23 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 14:45 Aktemur, Tankut Baris
2019-06-26 8:59 ` Aktemur, Tankut Baris
2019-07-19 20:12 ` Tom Tromey
2019-07-23 14:51 ` Keith Seitz
2019-07-23 15:52 ` Tom Tromey
2019-07-23 16:24 ` Aktemur, Tankut Baris [this message]
2019-07-23 16:52 ` Keith Seitz
2019-07-23 16:22 ` Aktemur, Tankut Baris
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=B98F7326B8E238409968F562D326E1A90D04ACBD@IRSMSX103.ger.corp.intel.com \
--to=tankut.baris.aktemur@intel.com \
--cc=gdb@sourceware.org \
--cc=keiths@redhat.com \
--cc=markus.t.metzger@intel.com \
--cc=tom@tromey.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).