From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0F1A53852C5F; Wed, 23 Nov 2022 15:32:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0F1A53852C5F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669217572; bh=Cp4X2cteEUT93oQeh2PlUD/dy9QG6XAeYMx6LAlnmB4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=s5Urnktcyor5dDLH6r25B9cLBaK1BeYbWGP1QsMvH7NtloTcX43vYHgCUIyr0LD+1 6r1XwXNPAQqpG/GT9oVbgRWP+Fp3l6k006f4OVn2uAiUCqizVXb42PpzGAP3l/EyzH jwOqLZNVgx9+mjDqNlWVqm9tWEylLW2lk65Ix84U= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/107815] 20_util/to_chars/float128_c++23.cc FAILs Date: Wed, 23 Nov 2022 15:32:49 +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.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: 13.0 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=3D107815 --- Comment #6 from Jonathan Wakely --- (In reply to Jakub Jelinek from comment #5) > Jonathan, shall we just #ifdef out the > std::numeric_limits::max() > test in that test for Solaris and maybe HP-UX if it suffers from the same > bug? Yes, I don't see any point trying to fix the output here. Let's just skip t= hose tests that are known to fail (with a comment mentioning this PR).=