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 1DC8D3858008; Tue,  4 Jan 2022 16:13:45 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1DC8D3858008
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103904] [defect fix] Please backport P2325R3 to 10
 and 11
Date: Tue, 04 Jan 2022 16:13:44 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 11.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
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-103904-4-ZADwu5qmkh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-103904-4@http.gcc.gnu.org/bugzilla/>
References: <bug-103904-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2022 16:13:45 -0000

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

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The issue is whether somebody's code breaks when upgrading from GCC 11.2 to
11.3, or when upgrading from 11.x to 12.x, and the documented policy says t=
he
former should be avoided. https://gcc.gnu.org/develop.html#release says

-->8--
Changes Appropriate for Bug-Fix Releases

As a general rule of thumb, bug-fix releases should contain fixes for
regressions or serious bugs uncovered in the corresponding major release of=
 GCC
or those prior to it. When backporting patches from subsequent releases or =
from
trunk, care should be taken to avoid making changes that cause previously
accepted code to be rejected unless doing so would cause GCC to generate
incorrect object code or code with undefined behavior.

Rationale

Users have an expectation of upgrading to a bug-fix GCC release without hav=
ing
to adjust their source code. Avoiding changes that reject code that was
previously accepted makes this possible.
-->8--

The only reason to consider breaking the policy is that C++20 support is
explicitly experimental, so breaking changes are more acceptable.=