public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/29896] GDB git doesn't recognize template function name
Date: Thu, 15 Dec 2022 14:28:28 +0000 [thread overview]
Message-ID: <bug-29896-4717-K9xNSAjPc3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29896-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29896
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
> Another idea is to change the hashing
I forgot the index uses a sorted vector, not a hash table.
I tried using strcmp_iw_ordered, but that doesn't really
have the right semantics. Now I'm working on a patch to
implement a custom comparison function.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-15 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 2:05 [Bug c++/29896] New: " vimacs.hacks at gmail dot com
2022-12-13 3:21 ` [Bug c++/29896] " simark at simark dot ca
2022-12-13 3:32 ` vimacs.hacks at gmail dot com
2022-12-13 19:33 ` tromey at sourceware dot org
2022-12-14 0:42 ` tromey at sourceware dot org
2022-12-15 14:28 ` tromey at sourceware dot org [this message]
2022-12-15 17:37 ` tromey at sourceware dot org
2022-12-15 19:08 ` tromey at sourceware dot org
2023-01-17 14:06 ` cvs-commit at gcc dot gnu.org
2023-01-17 14:15 ` cvs-commit at gcc dot gnu.org
2023-01-17 14:15 ` tromey at sourceware dot org
2023-01-18 22:08 ` tromey at sourceware dot org
2023-02-02 3:38 ` brobecker at gnat dot com
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=bug-29896-4717-K9xNSAjPc3@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).