Mail Archives: djgpp/2009/05/02/12:17:10
> From: "Charles Sandmann" <cwsdpmi AT earthlink DOT net>
> Date: Sat, 2 May 2009 10:28:29 -0500
>
> >"Eli Zaretskii" <eliz AT gnu DOT org> wrote in message
> >news:83y6tfem02 DOT fsf AT gnu DOT org...
> >> From: Rugxulo <rugxulo AT gmail DOT com>
> >> It also doesn't like "info all-regs", IIRC.
> >Yes, for the same reason: it thinks DJGPP supports SSE registers.
>
> What is required to make that work?
There are 2 possible fixes: the easy one and the more complicated one.
The easy one is a two-liner: tell GDB that we don't support SSE. I
already did that, and the patch is in the GDB CVS repository since
about 2 days ago. (The original problem happened because GDB switched
to supporting SSE by default in its x86 targets at some point, so any
target that doesn't support them needs to explicitly disable that.
Seems like no one from the DJGPP camp, yours truly included, payed
attention at the time.)
The more complex solution is to extend save_npx and load_npx to use
FXSAVE and FXRSTOR instructions, when they are available, instead of
FNSAVE and FRSTOR that we use now. But that means hacking the library
or providing GDB-private versions of these functions. Unless many
DJGPP users need access to SSE registers (which sounds improbable,
given that this feature is badly broken for at least 5 last years), I
don't see a justification for this hassle.
- Raw text -