public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65598] Fix column location for 'explicit'
Date: Fri, 22 May 2015 14:15:00 -0000	[thread overview]
Message-ID: <bug-65598-4-jWtN8IhWbK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65598-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> ---
Author: paolo
Date: Fri May 22 14:14:38 2015
New Revision: 223576

URL: https://gcc.gnu.org/viewcvs?rev=223576&root=gcc&view=rev
Log:
/cp
2015-05-22  Paolo Carlini  <paolo.carlini@oracle.com>

        PR c++/65598
        * decl.c (grokdeclarator): Use the correct location in error
        messages about 'explicit'.

/testsuite
2015-05-22  Paolo Carlini  <paolo.carlini@oracle.com>

        PR c++/65598
        * g++.dg/cpp0x/explicit9.C: New.
        * g++.dg/cpp0x/explicit8.C: Check the locations too.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/explicit9.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/decl.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/g++.dg/cpp0x/explicit8.C


  parent reply	other threads:[~2015-05-22 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 10:29 [Bug c++/65598] New: Misleading error message for out-of-class definition of explicit conversion operator arvo at me dot com
2015-03-27 11:17 ` [Bug c++/65598] " redi at gcc dot gnu.org
2015-03-27 11:29 ` redi at gcc dot gnu.org
2015-03-27 13:15 ` [Bug c++/65598] Fix column location for 'explicit' manu at gcc dot gnu.org
2015-04-22 11:57 ` jakub at gcc dot gnu.org
2015-05-22 11:03 ` paolo.carlini at oracle dot com
2015-05-22 14:15 ` paolo at gcc dot gnu.org [this message]
2015-05-22 14:15 ` 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-65598-4-jWtN8IhWbK@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).