This is the mail archive of the
mailing list for the GDB project.
Re: floating point registers in 'info reg'
- To: Fernando Nasser <fnasser at redhat dot com>
- Subject: Re: floating point registers in 'info reg'
- From: jtc at redback dot com (J.T. Conklin)
- Date: 09 Jan 2001 15:18:21 -0800
- Cc: gdb at sourceware dot cygnus dot com
- References: <firstname.lastname@example.org> <3A5B9A5C.2677F19@redhat.com>
- Reply-To: jtc at redback dot com
>>>>> "Fernando" == Fernando Nasser <email@example.com> writes:
>> While just a nit, this has been bothering me for some time.
>> The 'info reg' command is supposed to output only non-fpu registers,
>> but it uses the following expression to determine whether a register
>> is floating point:
>> TYPE_CODE (REGISTER_VIRTUAL_TYPE (i)) == TYPE_CODE_FLT
>> which means that FPU control and status registers are output. Is
>> there a better way to determine which registers are FP and which are
Fernando> Well, the problem is that FPU control and status registers
Fernando> should not have TYPE_CODE_FLT as virtual type. The data FPU
Fernando> registers are, but not the control ones.
That's not the problem. For example, on the x86, the fctrl, fstat,
ftag, ... registers don't have TYPE_CODE_FLT as a virtual type. But
since that test is used to determine whether a register is considered
to be a floating point register, "info reg" will output the values of
those registers. On those targets that a separate command to fetch FP
registers, this adds additional command latency.