From: Ian Lance Taylor <iant@google.com>
To: Jeff Law <law@redhat.com>
Cc: Mikhail Maltsev <maltsevm@gmail.com>,
gcc-patches <gcc-patches@gnu.org>,
Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH 3/7] Fix trinary op
Date: Wed, 08 Jul 2015 10:55:00 -0000 [thread overview]
Message-ID: <CAKOQZ8y4GXBR=FL2r0fiwkGNPLTS8SV8=BjiCpFaRWHv-pvuTA@mail.gmail.com> (raw)
In-Reply-To: <559C5547.2020700@redhat.com>
On Tue, Jul 7, 2015 at 3:40 PM, Jeff Law <law@redhat.com> wrote:
>
> And a generic question on the testsuite -- presumably it turns on type
> demangling? I wanted to verify the flow through d_expression_1 was what I
> expected it to be and it took a while to realize that c++filt doesn't
> demangle types by default, thus Av32_f would demangle to Av32_f without ever
> getting into d_expression_1.
The testsuite passes DMGL_TYPES to the demangler (see
libiberty/testsuite/test-demangle.c). The c++filt program does not
use DMGL_TYPES by defaut (you can turn it on with the -t option).
I don't know of anybody who actually uses the DMGL_TYPES support. I
don't know why anybody would.
Ian
next prev parent reply other threads:[~2015-07-08 10:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 19:18 [PATCH 0/7] Fix bugs found during demangler fuzz-testing Mikhail Maltsev
2015-07-06 19:22 ` [PATCH 1/7] Add CHECK_DEMANGLER Mikhail Maltsev
2015-07-06 22:50 ` Jeff Law
2015-07-06 19:24 ` [PATCH 2/7] Fix build with CP_DEMANGLE_DEBUG Mikhail Maltsev
2015-07-06 22:19 ` Jeff Law
2015-07-06 19:26 ` [PATCH 3/7] Fix trinary op Mikhail Maltsev
2015-07-07 22:39 ` Jeff Law
2015-07-08 10:55 ` Ian Lance Taylor [this message]
2015-07-08 13:42 ` Tom Tromey
2015-07-08 13:46 ` Ian Lance Taylor
2015-07-10 4:50 ` Mikhail Maltsev
2015-07-10 20:44 ` Jeff Law
2015-07-13 5:54 ` Mikhail Maltsev
2015-07-06 19:28 ` [PATCH 4/7] Fix int overflow Mikhail Maltsev
2015-07-06 22:55 ` Jeff Law
2015-07-07 0:05 ` Mikhail Maltsev
2015-07-07 22:48 ` Jeff Law
2015-07-08 3:58 ` Mikhail Maltsev
2015-07-08 10:52 ` Ian Lance Taylor
2015-07-06 19:28 ` [PATCH 5/7] Fix braced-init-list demangling Mikhail Maltsev
2015-07-06 22:58 ` Jeff Law
2015-07-06 19:31 ` [PATCH 6/7] Fix DEMANGLE_COMPONENT_LOCAL_NAME Mikhail Maltsev
2015-07-07 22:40 ` Jeff Law
2015-07-06 19:32 ` [PATCH 7/7] Fix several crashes in d_find_pack Mikhail Maltsev
2015-07-07 22:50 ` Jeff Law
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='CAKOQZ8y4GXBR=FL2r0fiwkGNPLTS8SV8=BjiCpFaRWHv-pvuTA@mail.gmail.com' \
--to=iant@google.com \
--cc=gcc-patches@gnu.org \
--cc=jason@redhat.com \
--cc=law@redhat.com \
--cc=maltsevm@gmail.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).