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 45DAE3858C56; Fri, 19 Jan 2024 13:44:42 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 45DAE3858C56
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705671882;
	bh=iNnW6xsPcaMXXOODgqRF06JZRI0zAy1L2kCpguYLuME=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=B3pAh7EqF2RnXHBEUHtPi6eZDi58HfgY5pvoR074mcGjZatdTw3GG+1DD3vELaWfm
	 rp3+j862fHx4lA9XTMQJ0GmSwJmukBBilDeOFyVJkeSCvWvfgT0i8hcoN2Wdef6E+g
	 CL8GIUak/gi7a65MfrMaYIHJCiPebPM+Mj5Ep6BA=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/113500] Using std::format with float or double based
 std::chrono::time_point causes error: no match for 'operator<<'
Date: Fri, 19 Jan 2024 13:44:41 +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: 
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.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113500-4-tus5JpxfV5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113500-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113500-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=3D113500

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #6)
> (In reply to Hirthammer from comment #5)
> > This whole thing with std::format and std::chrono::time_point is curren=
tly a
> > total minefield.
>=20
> That seems like an exaggeration.
>=20
> > In MSVC it is even more complicated and I already reported
> > the bug in October 2023. See:
> >=20
> > https://developercommunity.visualstudio.com/t/Using-std::format-with-
> > unsigned-integer-/10501153
> >=20
> > If you change the clock to utc_clock or gps_clock the code compiles with
> > MSVC (but not with GCC) on Compiler Explorer.
>=20
> It compiles fine with GCC for me.

Ah, maybe you mean your original example. The one at in the MSVC bug report
compiles fine with GCC using utc_clock and gps_clock.

Your original example doesn't, because formatting a utc_time or gps_time is
specified in terms of a sys_time, and that's how libstdc++ implements it. S=
o if
the utc_time or gps_time uses a float rep, we're back to square one.

I'll ask the committee to clarify that too.=