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 2550A3858D35; Mon,  8 May 2023 16:32:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2550A3858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683563553;
	bh=qpeFdi6ZUh6xd9UkAyYRpbWrXvokP71PnpC3aPb6X3o=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=i9aD/RoKI1cw/usrqAJdIHFoVpo+Vmd1VYFuSKdzWuXCj2NiFrmH5G2Pl0/Da88t4
	 MNXAFeSS0NxTxACJILwsv4OotS4Tj5I4EsBJkQiosuhUIyKjUZBsHv+/HXIwX2uQQq
	 L3yrSCA9eznxuw29pSFbA6gzRH6dtOMwh1QPAC54=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109772] Memory layout optimization of
 std::chrono::hh_mm_ss is wrong
Date: Mon, 08 May 2023 16:32:33 +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: 13.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.2
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109772-4-KQ4gIdnMPC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109772-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=3D109772

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Or if problematic uses of hh_mm_ss are as rare as I expect, we could just n=
ot
fix it on the gcc-13 branch, only on trunk.=