From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8E8E33851C0E; Mon, 22 Jun 2020 10:01:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8E8E33851C0E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1592820090; bh=pSF69dZJjudOuxDoiCm4CNFIqwnFaQZOzznnnaLZOuE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=HKMitGHfd5+SQXikegqu6vWHUFWnmgGpgvZmEGPewxgNEpMR54OQ3gYCu/LOtV52q YtF2lDfRbyU+hLQCnqu11gnRlXZyHt3YKN8unjvJkpZw3DWW+LOHXwXMgRM0c8C1Zz 9g59REA+LlzrE4YU7rsbY1hPokU6cOimiAdmDJ7E= From: "haoxintu at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95807] GCC accepts "void value not ignored as it ought to be" in function template Date: Mon, 22 Jun 2020 10:01:30 +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: 11.0 X-Bugzilla-Keywords: accepts-invalid X-Bugzilla-Severity: normal X-Bugzilla-Who: haoxintu at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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: Mon, 22 Jun 2020 10:01:30 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95807 --- Comment #4 from Haoxin Tu --- (In reply to Jonathan Wakely from comment #3) > The ill-formed template is not diagnosed unless you instantiate it. > That is allowed by the standard. Thank you Jonathan, thanks for your response. As other major compilers reject this by default, I just suggest GCC should = emit a appropriate diagnostic message (maybe a warning is fine). Just a suggestion, please understand if it is inappropriate ~=