Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gcc-patches@gcc.gnu.org,
	Gabriel Dos Reis <gdr@integrable-solutions.net>,
	       gdb-patches@sourceware.org
Subject: Re: [gcc patch] Re: C++ member function template id not matching linkage name (PR debug/49408)
Date: Wed, 29 Jun 2011 20:56:00 -0000	[thread overview]
Message-ID: <4E0B917A.7040508@redhat.com> (raw)
In-Reply-To: <20110629200004.GA10065@host1.jankratochvil.net>

On 06/29/2011 04:00 PM, Jan Kratochvil wrote:
> On Mon, 27 Jun 2011 20:00:24 +0200, Jason Merrill wrote:
>> They should be supressed whenever the function appears in an
>> expression context, either as a pointer to member function (i.e. the
>> operand of '&')
> 
> Done, therefore it is no longer restricted only to templates as before.
> 
>> or as the function being called in a call expression.
> 
> I implemented it in the patch below but I do not agree + understand it.
> 
> The call expression is in libiberty/testsuite/demangle-expected modified by
> this patch as:
> 
>   # decltype/fn call test
>   --format=gnu-v3
>   _Z4add3IidEDTclL_Z1gEfp_fp0_EET_T0_
> -decltype (g({parm#1}, {parm#2})) add3<int, double>(int, double)
> +decltype (g) add3<int, double>(int, double)

Here you're suppressing the arguments to a call, which we want to keep;
we only want to suppress printing the parameter types (which are not
part of the source expression).

Jason


  reply	other threads:[~2011-06-29 20:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTimFFWA1mOZKMbV7Ufe2mgiD5o7H1w@mail.gmail.com>
     [not found] ` <4E020D6A.7030401@redhat.com>
2011-06-27 15:05   ` Jan Kratochvil
2011-06-27 18:00     ` Jason Merrill
2011-06-29 20:00       ` Jan Kratochvil
2011-06-29 20:56         ` Jason Merrill [this message]
2011-06-29 21:07           ` Jan Kratochvil
2011-06-29 22:28             ` Jason Merrill
2011-06-30 21:00               ` Jan Kratochvil
2011-07-01 17:07                 ` Jason Merrill
2011-07-01 17:21                   ` Jan Kratochvil

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=4E0B917A.7040508@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gdr@integrable-solutions.net \
    --cc=jan.kratochvil@redhat.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