Date: Tue, 28 Nov 2023 15:47:55 +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-AEmYyXT7XW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275322-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275322 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markj@FreeBSD.org --- Comment #7 from Mark Johnston <markj@FreeBSD.org> --- When I run this on a Ryzen 7950X3D running main, I get: ra=7.01209994486364354e-310 reatt=10000000000 ra * reatt-> result =0 savemxcsr 00001f80 mxcsr_set 00009fc0 showmxcsr 00009fc0 mxcsr 00009fc0 when I have a breakpoint on the "mulsd" instruction: ra=7.01209994486364354e-310 reatt=10000000000 ra * reatt-> result =0 savemxcsr 00001f80 mxcsr_set 00009fc0 showmxcsr 00009fc0 mxcsr 00009fc0 while stopped at "mulsd": (gdb) info register mxcsr mxcsr 0x1f80 [ IM DM ZM OM UM PM ] (gdb) c Continuing. ra=7.01209994486364354e-310 reatt=10000000000 ra * reatt-> result =7.01209994486364403e-300 savemxcsr 00001f80 mxcsr_set 00009fc0 showmxcsr 00009fc0 mxcsr 00001fa2 So I believe the problem is reproducible here. In particular, the output of the test program varies depending on whether I print the value of mxcsr from gdb or not. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275322-227-AEmYyXT7XW>