Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>, Nick Clifton <nickc@redhat.com>
Cc: Jason Merrill <jason@redhat.com>,
	Ian Lance Taylor <iant@google.com>,
	Richard Biener <richard.guenther@gmail.com>,
	matz@gcc.gnu.org, Scott Gayou <sgayou@redhat.com>,
	Tom Tromey <tom@tromey.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: Fri, 07 Dec 2018 16:11:00 -0000	[thread overview]
Message-ID: <aff87924-f257-733c-cb6c-0b45dd1a9684@redhat.com> (raw)
In-Reply-To: <20181207104011.GD12380@tucnak>

Adding gdb-patches, since demangling affects gdb.

Ref: https://gcc.gnu.org/ml/gcc-patches/2018-12/msg00407.html

On 12/07/2018 10:40 AM, Jakub Jelinek wrote:
> On Fri, Dec 07, 2018 at 10:27:17AM +0000, Nick Clifton wrote:
>>>> Looks good to me.  Independently, do you see a reason not to disable the
>>>> old demangler entirely?
>>>
>>> Like so.  Does anyone object to this?  These mangling schemes haven't
>>> been relevant in decades.
>>
>> I am not really familiar with this old scheme, so please excuse my ignorance
>> in asking these questions:
>>
>>   * How likely is it that there are old toolchain in use out there that still 
>>     use the v2 mangling ?  Ie I guess that I am asking "which generation(s)
>>     of gcc used v2 mangling ?"
> 
> GCC 3.0 and up used the new (Itanium C++ ABI) mangling, 2.95 and older used the old
> mangling (2.96-RH used the new mangling I believe).
> So you need compiler older than 17.5 years to have the old mangling.
> Such a compiler didn't support most of the contemporarily used platforms
> though at all (e.g. x86-64, powerpc64le, aarch64, I believe not even
> powerpc64-linux).
> 
Yeah.

I guess the question would be whether it is reasonable to expect
that people will still need to debug&inspect (with gdb, c++filt, etc.)
any such old binary, and that they will need to do it with with modern
tools, as opposed to sticking with older binutils&gdb, and how often
would that be needed.

I would say that it's very, very unlikely, and not worth it of the
maintenance burden.

Last I heard of 2.95-produced binaries I think was for some ancient gcc-2.95-based
cross compiler that was still being minimally maintained, because it was needed
to build&maintain some legacy stuff.  That was maybe over 8 years ago, and
it was off trunk.  It's probably dead by now.  And if isn't dead,
whoever maintains the compiler off trunk certainly can also maintain old-ish
binutils & gdb off trunk.

Thanks,
Pedro Alves


       reply	other threads:[~2018-12-07 16:11 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 [this message]
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

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=aff87924-f257-733c-cb6c-0b45dd1a9684@redhat.com \
    --to=palves@redhat.com \
    --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=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