Date: Wed, 6 Feb 2002 17:40:58 -0500 From: Alexander Kabaev <ak03@gte.com> To: Daniel Eischen <eischen@pcnet1.pcnet.com> Cc: peter@wemm.org, eischen@vigrid.com, arch@FreeBSD.ORG Subject: Re: getsetcontext system call Message-ID: <20020206174058.60c8cf14.ak03@gte.com> In-Reply-To: <Pine.GSO.4.10.10202061700570.29032-100000@pcnet1.pcnet.com> References: <20020206195918.6350039F1@overcee.wemm.org> <Pine.GSO.4.10.10202061700570.29032-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> As to set_fpregs(), it looks like it wants to convert an x87 > FPU state to an SSE FPU state. The opposite seems to be the > case for fill_fpregs(). I'm not exactly sure how and why > fill_fpregs() and set_fpregs() are used. Since we make struct > fpreg large enough to hold either x87 or SSE FPU state, do we > even care about converting between the two different formats > any longer? These functions are used by ptrace and consequently by GDB. GDB expects to get floating point register state in predictable format regardless of whether SSE has been enabled in CPU or not. Linux also adds new GET/SET_FPXREGS requests to get complete SSE floating point registers for use by SSE aware debuggers. As far as I can tell, GDB 5.x is using these new requests on Linux, while 4.18 doesn't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020206174058.60c8cf14.ak03>