From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8B3ED3850434; Thu, 7 Jan 2021 17:55:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8B3ED3850434 From: "ppalka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98384] [11 Regression] new test case 20_util/to_chars/long_double.cc in r11-6249 fails on powerpc64 BE Date: Thu, 07 Jan 2021 17:55:10 +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.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ppalka at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ppalka at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2021 17:55:10 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D98384 --- Comment #6 from Patrick Palka --- (In reply to Iain Sandoe from comment #4) > (In reply to Patrick Palka from comment #3) > > Candidate patch: > > https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563000.html >=20 > thanks! >=20 > On Darwin, the test case now builds (checked on a 32b host [powerpc] with= a > 64b multilib) and a 64b (x86_64) host. The 32b multilib xfails the execu= te > (as expected w/out int128 support) >=20 > On both powerpc (64b multilib) and x86_64: >=20 > test01 fails with :=20 > src-local/gcc-master/libstdc++-v3/testsuite/20_util/to_chars/long_double.= cc: > 136: void test01(): Assertion '!strcmp(to_chars_buffer, > printf_buffer+strlen("0x"))' failed. >=20 > (not analysed why yet). Thanks for testing! Hmm, that execute failure is surprising. I wonder just how much we're diverging from the output of printf here. If possible, could you let me know the value of the locals 'to_chars_buffer', 'printf_buffer', 'precision' and 'testcase' (ideally in hex form) at the point of the assert= ion failure?=