From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 859D03858D35; Sun, 19 Apr 2020 04:44:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 859D03858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1587271489; bh=clAr4J36kjGLfmm2fiHAsZO4Vc0ICemOccNNDC1nbM4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TThwPWaW8cwQidUMXWGNLIEC5rpvzmmbluRxuNvpq/9SIVDtlxXTmfOYcyNY/Tfub EGwEKa6C3L3P8NvkOVigocUdE+xyDy1pa/1uM6X4gQtazGe3VSx/1ZfdBTeAIyvezJ eTs94mEiQ8N4oI5fxLCTO2KhbFc0GOQkx22YzTOQ= From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94310] using constructor inheritance breaks the code Date: Sun, 19 Apr 2020 04:44:49 +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: 9.2.1 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2020 04:44:49 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94310 --- Comment #2 from Marek Polacek --- The difference stems from the fact that in this test: template struct B { }; template struct A : public B... { using B::B...; // #1 using B::operator=3D...; // #2 }; int main() {} when parsing B in #2 cp_parser_lookup_name finds #1, which is a dependent USING_DECL. strip_using_decl doesn't do anything with such a USING_DECL, so we think that we haven't found a template name.=