From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb.dlang/demangle.exp: update expected output for _D8demangle4testFnZv
Date: Fri, 14 Jan 2022 13:12:41 -0700 [thread overview]
Message-ID: <875yqmf552.fsf@tromey.com> (raw)
In-Reply-To: <20220113161016.2248240-1-simon.marchi@efficios.com> (Simon Marchi via Gdb-patches's message of "Thu, 13 Jan 2022 11:10:16 -0500")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> Note: it's not really useful to have all these D demangling tests in the
Simon> GDB testsuite, since there are demangling tests in libiberty.
Funny story, the libiberty demangler test suite actually started as a
copy of gdb's demangler tests, back in ancient times.
I wouldn't mind removing the gdb copies though. I don't think they add
much value. If need be I guess we could figure out a way to add unit
testing to libiberty and run that from gdb's selftests.
Tom
prev parent reply other threads:[~2022-01-14 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 16:10 Simon Marchi
2022-01-14 19:45 ` Iain Buclaw
2022-01-14 20:09 ` Simon Marchi
2022-01-14 20:12 ` Tom Tromey [this message]
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=875yqmf552.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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).