[Bug c++/63263] New: friend declaration of template specialization of function gets confused when specialization was forward declared

[Bug c++/63263] New: friend declaration of template specialization of function gets confused when specialization was forward declared

[carlo at gcc dot gnu.org]

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

            Bug ID: 63263
           Summary: friend declaration of template specialization of
                    function gets confused when specialization was forward
                    declared
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: carlo at gcc dot gnu.org

The following code snippet should compile, but it doesn't.

template<typename T>
void f(T&, float&)
{
  T(1);
}

struct B;

template<>
void f(B&, float&)
{
}

struct B {
  friend void f<B>(B&, float&);
};

void g()
{
  B b;
  float n;
  f(b, n);
}

The result is:

troep.cc: In instantiation of ‘void f(T&, float&) [with T = B]’:
troep.cc:22:9:   required from here
troep.cc:4:3: error: no matching function for call to ‘B::B(int)’
troep.cc:4:3: note: candidates are:
troep.cc:14:8: note: B::B()
troep.cc:14:8: note:   candidate expects 0 arguments, 1 provided
troep.cc:14:8: note: B::B(const B&)
troep.cc:14:8: note:   no known conversion for argument 1 from ‘int’ to ‘const
B&’
troep.cc:4: confused by earlier errors, bailing out
Preprocessed source stored into /tmp/ccjzbrcd.out file, please attach this to
your bugreport.

If I either comment out the friend declaration, or move the
specialization to after the struct B declaration (so that the
friend declaration caused the specialization), then it compiles
and works.

clang compiles this fine.
>From gcc-bugs-return-461800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Sep 14 21:22:26 2014
Return-Path: <gcc-bugs-return-461800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22751 invoked by alias); 14 Sep 2014 21:22:26 -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 22730 invoked by uid 48); 14 Sep 2014 21:22:23 -0000
From: "carlo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63263] friend declaration of function template specialization gets confused when specialization was forward declared.
Date: Sun, 14 Sep 2014 21:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.7.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: carlo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63263-4-RckJLwu22y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63263-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-09/txt/msg01634.txt.bz2
Content-length: 284

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

--- Comment #1 from Carlo Wood <carlo at gcc dot gnu.org> ---
Guess the float isn't needed:

template<typename T> void f(T&) { T(1); }
struct B;
template<> void f(B&) { }
struct B { friend void f<B>(B&); };
void g() { B b; f(b); }

[Bug c++/63263] friend declaration of function template specialization gets confused when specialization was forward declared.

[pinskia at gcc dot gnu.org]

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
With the trunk I get an ICE too:
t.cc: In instantiation of ‘void f(T&, float&) [with T = B]’:
t.cc:22:9:   required from here
t.cc:4:3: error: no matching function for call to ‘B::B(int)’
   T(1);
   ^
t.cc:14:8: note: candidate: B::B()
 struct B {
        ^
t.cc:14:8: note:   candidate expects 0 arguments, 1 provided
t.cc:14:8: note: candidate: B::B(const B&)
t.cc:14:8: note:   no known conversion for argument 1 from ‘int’ to ‘const B&’
t.cc:4:7: internal compiler error: in add_stmt, at cp/semantics.c:395
   T(1);
       ^
Please submit a full bug report,
with preprocessed source if appropriate.
>From gcc-bugs-return-461803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Sep 14 22:05:36 2014
Return-Path: <gcc-bugs-return-461803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4084 invoked by alias); 14 Sep 2014 22:05:36 -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 4065 invoked by uid 48); 14 Sep 2014 22:05:31 -0000
From: "mikulas at artax dot karlin.mff.cuni.cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63264] New: Internal error due to invalid assembler register specification
Date: Sun, 14 Sep 2014 22:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikulas at artax dot karlin.mff.cuni.cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-63264-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-09/txt/msg01637.txt.bz2
Content-length: 1044

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

            Bug ID: 63264
           Summary: Internal error due to invalid assembler register
                    specification
           Product: gcc
           Version: 4.9.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mikulas at artax dot karlin.mff.cuni.cz
              Host: x86_64-linux-gnux32
            Target: x86_64-linux-gnux32
             Build: x86_64-linux-gnux32

This piece of code:
void f(unsigned x)
{
        __asm__ volatile ("xorl %R0, %R0":"=r"(x):"r"(x):"cc");
}
triggers this internal error:
asm-crash.c: In function 'f':
asm-crash.c:4:1: internal compiler error: in ix86_print_operand, at
config/i386/i386.c:15214
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

The error happens in i386, x86-64 and x32 mode. With or without optimization.

[Bug c++/63263] friend declaration of function template specialization gets confused when specialization was forward declared.

[ville.voutilainen at gmail dot com]

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

Ville Voutilainen <ville.voutilainen at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |rejects-valid
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-12-13
                 CC|                            |ville.voutilainen at gmail dot com
     Ever confirmed|0                           |1
      Known to fail|                            |4.8.2, 4.9.1, 5.0

--- Comment #3 from Ville Voutilainen <ville.voutilainen at gmail dot com> ---
Trunk no longer ICEs. Clang accepts the code.