This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [WIP/RFC] MIPS registers overhaul


On Wed, May 14, 2003 at 05:07:16PM -0700, Kevin Buettner wrote:
> On May 14,  4:34pm, cgd@broadcom.com wrote:
> 
> > In other words, the real arbiter of the unpredictability of those bits
> > is Status:FR, so you should probably display them consistently with
> > what it says (if you have Status... I forget 8-).
> 
> I see the following in mips2_fp_compat():
> 
> #if 0
>   /* FIXME drow 2002-03-10: This is disabled until we can do it consistently,
>      in all the places we deal with FP registers.  PR gdb/413.  */
>   /* Otherwise check the FR bit in the status register - it controls
>      the FP compatiblity mode.  If it is clear we are in compatibility
>      mode.  */
>   if ((read_register (PS_REGNUM) & ST0_FR) == 0)
>     return 1;
> #endif
> 
> I don't know the details, but it appears that there may be problems
> with consistently being able to fetch the status register.  (Maybe
> it's not available on all MIPS targets that GDB supports?)
> 
> Anyone know?

Hmm, I vaguely remember writing that.  I don't think that's what I
meant by consistent - I just meant that we needed to use that function
everywhere appropriate.  I believe Status is always available, so we
could use it to choose which FP registers are exposed.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]