From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5108B3858C74; Fri, 19 Jan 2024 08:14:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5108B3858C74 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1705652085; bh=bDj4IeJp8/h3HMtTqLXot4pH/RTpBEozgN7GSI8NI/E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=J6qxPmhkrpdVIiQilxKyXUAEU8alu+wT04vwVbqWoB1FO4gw1adzDoAJi7ypgYuwE crv1e3Az7IX+muLtt0VkurvrZzxWK5kc2P2oPcUQu4oq9vQkwvL8z0KAwIubrs7ZRY jUcoh1JipYQ082oHIY85DVW09vRMmeICa2ROHsN4= From: "Hirthammer@allterra-dno.de" 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 08:14:45 +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: Hirthammer@allterra-dno.de 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: 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=3D113500 --- Comment #3 from Hirthammer@allterra-dno.de --- Sorry, for the missing includes. > Since this is a bug in libstdc++ headers it's not at all surprising that = you get=20 > the same error with any compiler using those headers. This should not hav= e been=20 > reported to llvm. Thanks for clarifying this.=