Date: Tue, 28 Nov 2023 16:53:49 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275322] Improper handling of mxcsr register during debug (gdb/lldb) Message-ID: <bug-275322-227-4rDVzoB7ZR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275322-227@https.bugs.freebsd.org/bugzilla/> References: <bug-275322-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275322 Olivier Certner <olivier.freebsd@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |olivier.freebsd@free.fr --- Comment #8 from Olivier Certner <olivier.freebsd@free.fr> --- On a bare-metal Ryzen 3900X running 13-STABLE, I get: ra=3D7.01209994486364354e-310 reatt=3D10000000000 ra * reatt-> result =3D0 = savemxcsr 00001f80 mxcsr_set 00009fc0 showmxcsr 00009fc0 mxcsr 00009fc0 With a breakpoint I see the same, and when stopped at "mulsd": (gdb) info register mxcsr mxcsr 0x1f80 [ IM DM ZM OM UM PM ] (gdb) continue Continuing. ra=3D7.01209994486364354e-310 reatt=3D10000000000 ra * reatt-> result =3D7.01209994486364403e-300 savemxcsr 00001f80 mxcsr_set 00009fc0 showmxcsr 00009fc0 mxcsr 00001fa2 So I get the same results as markj@ (comment #7), and the same as Cheyenne Wills (comment #1) except for mxcsr in the first print (00009fc0). Given t= he code, I don't get how you can possibly obtain 00001f80. Anyway, there is a discrepancy between a normal run (and a debugged run without "info register mxcsr") and a debug run with "info register mxcsr"). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275322-227-4rDVzoB7ZR>