From: Simon Marchi <simark@simark.ca>
To: Jason Merrill <jason@redhat.com>, Tom Tromey <tom@tromey.com>,
Pedro Alves <palves@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>, Nick Clifton <nickc@redhat.com>,
Ian Lance Taylor <iant@google.com>,
Richard Biener <richard.guenther@gmail.com>,
matz@gcc.gnu.org, Scott Gayou <sgayou@redhat.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>,
Binutils <binutils@sourceware.org>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: RFC: libiberty PATCH to disable demangling of ancient mangling schemes
Date: Sun, 16 Dec 2018 04:50:00 -0000 [thread overview]
Message-ID: <2f543a8b-f440-5958-c5ce-3650db96d2e7@simark.ca> (raw)
In-Reply-To: <CADzB+2k4AgmoKZN=Cn9KgPF5qX5YqaSq19=h0+cGaXyC_PZeZQ@mail.gmail.com>
On 2018-12-14 5:39 p.m., Jason Merrill wrote:
> GDB/binutils folks, how do you want to handle this? Shall I go ahead
> with this patch, with the understanding that there will be associated
> changes necessary when merging it into the binutils-gdb repository, or
> go with the small disabling patch to start with?
Hi Jason
From the GDB point of view, I don't see any problem. Please proceed with
the cleanup, it should be quite easy to adjust our code when we sync libiberty.
There is a usage of cplus_mangle_opname in binutils/stabs.c, and I can't
speak for binutils. But speaking of cplus_mangle_opname, shouldn't you also
remove the declaration in include/demangle.h?
Simon
prev parent reply other threads:[~2018-12-16 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa1abe9c-7545-6a48-cbf0-97b993345523@redhat.com>
[not found] ` <CAFiYyc1gTSXgSiJSFKEWaE0UTGbi45-mWHKJnUb4Wvjp86bbFQ@mail.gmail.com>
[not found] ` <460cb971-0e21-1e3e-4920-8b3ee7290cf7@redhat.com>
[not found] ` <CAKOQZ8zspME4gzoRw4xgFcShoqeUfp_e=Og=4S-yKn4EehokeA@mail.gmail.com>
[not found] ` <736e8303-b724-f96d-54f5-46bff99fa34d@redhat.com>
[not found] ` <57d33aa7-4e37-a09c-4bdc-974b5f654d33@redhat.com>
[not found] ` <c7c959ca-b8bf-bd3e-a65d-bb274a3118d3@redhat.com>
[not found] ` <2928eac9-9363-ddb8-21eb-df878d2d4837@redhat.com>
[not found] ` <CADzB+2n6kz=9zLzordWp3gqW+hrLHBhQJ-5p5Lt8Stqv97=nBw@mail.gmail.com>
[not found] ` <e720841c-fc62-fef5-559b-442b2a30f776@redhat.com>
[not found] ` <20181207104011.GD12380@tucnak>
2018-12-07 16:11 ` Pedro Alves
2018-12-07 17:49 ` Tom Tromey
2018-12-07 21:01 ` Jason Merrill
2018-12-14 22:39 ` Jason Merrill
2018-12-16 4:50 ` Simon Marchi [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=2f543a8b-f440-5958-c5ce-3650db96d2e7@simark.ca \
--to=simark@simark.ca \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=iant@google.com \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=matz@gcc.gnu.org \
--cc=nickc@redhat.com \
--cc=palves@redhat.com \
--cc=richard.guenther@gmail.com \
--cc=sgayou@redhat.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