From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EDE4A3973001; Fri, 8 Jan 2021 09:30:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EDE4A3973001 From: "ro at CeBiTec dot Uni-Bielefeld.DE" 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: Fri, 08 Jan 2021 09:30:23 +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: ro at CeBiTec dot Uni-Bielefeld.DE 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: Fri, 08 Jan 2021 09:30:24 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D98384 --- Comment #7 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #6 from Patrick Palka --- [...] > Thanks for testing! Hmm, that execute failure is surprising. I wonder j= ust > how much we're diverging from the output of printf here. If possible, co= uld > 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 asse= rtion > failure? I'm seeing exactly the same failure mode on Solaris, both sparc and x86: 32-bit compilation PASSes, execution XFAILed, 64-bit compilation PASSes, too, but execution FAILs with the same assertion failure. Here's what gdb prints for those variables (with the test compiled with -g3 -O0 where the assertion still fails): (gdb) p to_chars_buffer $1 =3D "f.", 'f' , "ep+5380", '\000' (gdb) p printf_buffer $2 =3D "0x1.", 'f' , "cp+5383", '\000' (gdb) p precision No symbol "precision" in current context. (gdb) p testcase $3 =3D 5.56540347525605847154e+1620 (gdb) p/x testcase $5 =3D 0x7fffffffffffffff=