From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2AEF43858408; Fri, 26 May 2023 20:35:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2AEF43858408 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1685133318; bh=D+wLvIHP5U1BwRS3+IV9Koyst5m15VJ54+8jA2wTJNk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=C6mtdJGBeWGrBFWrlexSMXyP6+wyvSJLsr6JBvS9EsLAdMornRdCG+1uqAO2v8NRc sx5eNGqIa0+vLdF9x/oO9Uya+8IFEGE4m0NiShD5McBQXgZiME5O2rt6rQLTsXel5U j/9zPzcIIDnEW3vCV9fAseH6s8WwSWef31qJg1/w= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110000] GCC should implement exclude_from_explicit_instantiation Date: Fri, 26 May 2023 20:35:18 +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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110000 --- Comment #3 from Andrew Pinski --- I am getting a feeling this attribute is well defined enough. Is it really just supposed to block explicit instantiation of templates? Is there a decent set of testcases that can be used to match up the implementations here? Because I suspect without those it will be implemented slightly different.=