public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/62101] New: deleted definitions of friend functions are rejected
Date: Tue, 12 Aug 2014 00:26:00 -0000	[thread overview]
Message-ID: <bug-62101-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 62101
           Summary: deleted definitions of friend functions are rejected
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ville.voutilainen at gmail dot com

Test:

struct X
{
    friend void f(X, int) = delete;
    friend void f(X, double) {}
};

struct Y;
void g(Y, int);
void g(Y, double);

struct Y
{
    friend void g(Y, int) = delete;
    friend void g(Y, double) {}
};

int main()
{
    X x;
    f(x, 5.0);
    Y y;
    g(y, 5.0);
}

deleted-friend.cpp:3:26: error: can’t initialize friend function ‘f’
  friend void f(X, int) = delete;
                          ^
deleted-friend.cpp:13:26: error: can’t initialize friend function ‘g’
  friend void g(Y, int) = delete;
                          ^

clang accepts the code. There doesn't seem to be any standard wording
forbidding in-class friend definitions that are deleted.
>From gcc-bugs-return-458219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Aug 12 00:33:42 2014
Return-Path: <gcc-bugs-return-458219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8494 invoked by alias); 12 Aug 2014 00:33:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8405 invoked by uid 48); 12 Aug 2014 00:33:31 -0000
From: "potswa at mac dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/58844] [4.8 Regression] ICE with invalid use of ##
Date: Tue, 12 Aug 2014 00:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: potswa at mac dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-58844-4-O3Uty1nEyI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58844-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg00716.txt.bz2
Content-length: 624

https://gcc.gnu.org/bugzilla/show_bug.cgi?idX844

David Krauss <potswa at mac dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |potswa at mac dot com

--- Comment #9 from David Krauss <potswa at mac dot com> ---
The fix makes the case well-formed. It's not. A sequence of concatenation
operators is not processed as if they were separated by empty parameters. "A ##
## B" concatenates A with the (second) ## to produce an illegal token "A##".
Clang diagnoses it as such.


             reply	other threads:[~2014-08-12  0:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  0:26 ville.voutilainen at gmail dot com [this message]
2014-08-14 17:12 ` [Bug c++/62101] " jason at gcc dot gnu.org
2014-08-15  8:21 ` 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-62101-4@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).