public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "abutcher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65750] [4.9/5 Regression] misinterpret in a virtual member function with a C++11 style function signature
Date: Mon, 13 Apr 2015 21:20:00 -0000	[thread overview]
Message-ID: <bug-65750-4-yhqLSXBoVH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65750-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65750

--- Comment #3 from Adam Butcher <abutcher at gcc dot gnu.org> ---
Agreed.  Upon seeing the 'auto' in the parameter list, we'll synthesize a
template parameter for 'g'.  I think Paolo added the diagnostic for virtual to
fix an ICE.

I'm not sure immediately how to handle this one.  For function pointer types
"auto (" should have this behavior.  Maybe we need a bit of look-ahead to solve
this (either for a function pointer or the trailing return arrow).

Looks like trying to tie down semantics at parse time is biting us again.


  parent reply	other threads:[~2015-04-13 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13  2:54 [Bug c++/65750] New: miss interpret " usagi at WonderRabbitProject dot net
2015-04-13  9:21 ` [Bug c++/65750] [4.9/5 Regression] misinterpret " redi at gcc dot gnu.org
2015-04-13 20:58 ` jason at gcc dot gnu.org
2015-04-13 21:20 ` abutcher at gcc dot gnu.org [this message]
2015-04-14  9:17 ` jakub at gcc dot gnu.org
2015-05-22 15:29 ` paolo.carlini at oracle dot com
2015-06-24 15:13 ` paolo.carlini at oracle dot com
2015-06-29  9:35 ` paolo at gcc dot gnu.org
2015-06-29  9:36 ` paolo.carlini at oracle dot com

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=bug-65750-4-yhqLSXBoVH@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).