From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 9D2C13857C48; Wed, 31 May 2023 16:52:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9D2C13857C48
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1685551945;
	bh=Mgep+94Rr7jF7ghXiGHL00OP+a+LIWZj3Xenj9vk1os=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=WPgU+ZTYyA8txS4jhQ7iDvMgwafbPho/ilCRwfAbOryc31kwTZZ5GyivfwDK6lX9l
	 Muc4UF/+bkwLgU8KCSybfWVBFXN2mGQpsFZxQCQJKzJjEHmZgBHctG/pykdQaKoBUC
	 YCr1JTp9YB8o9PvxUJN93UpqtTo2jFyqBb1lY3oI=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110000] GCC should implement
 exclude_from_explicit_instantiation
Date: Wed, 31 May 2023 16:52:25 +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: enhancement
X-Bugzilla-Who: redi 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: <bug-110000-4-qGvcOTDyt7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110000-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110000-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #10)
> Do you want to be able to change these functions in
> ABI-incompatible ways between major revisions of the library?

Sorry, that was unclear, I meant to ask if you want to change them in
ABI-incompatible ways without bumping the version in the abi_tag?

e.g. change std::__1::vector<int, std::__1::allocator<int>
>::__clear[abi:v15007]() in an ABI-incompatible way, without changing the t=
ag
to [abi:v15008]?

Because if the tag is going to change anyway, what does it matter if the us=
er
has instantiations of the old [abi:v15007] symbol in their lib?=