This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Help Translating Message from MIPS Simulator
- From: "Maciej W. Rozycki" <macro at imgtec dot com>
- To: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Sun, 16 Apr 2017 00:44:06 +0100
- Subject: Re: Help Translating Message from MIPS Simulator
- Authentication-results: sourceware.org; auth=none
- References: <1a3390f5-6456-d8bf-45b9-872c8be24a83@oarcorp.com>
On Sun, 16 Apr 2017, Joel Sherrill wrote:
> We have some RTEMS tests failing on the mips simulator
> in gdb. We are using the jmr3904 configuration and the
> run ends with this message:
>
> HILO: MFHI: MF at 0x88015698 following OP at 0x88000464 corrupted by MT at
> 0x88003c68
>
> 0x88000464 does appear to be in a reasonable location
> inside the test.
>
> How do I translate the rest to get an idea about the fault?
I'll give some background information.
In MIPS architecture HILO or HI/LO is the integer multiply-divide (MD)
unit's accumulator aka the HI and LO register pair. For widening
multiplication LO holds the low part of the product and HI holds the
corresponding high part. For division LO holds the quotient and HI holds
the remainder.
These registers are not a part of the general ALU and therefore special
operations have been defined to retrieve and also to store data there:
MFHI and MFLO (Move From HI/LO) are the read instructions and MTHI and
MTLO (Move To HI/LO) are the write instructions for the HI and the LO
register respectively.
In older architecture revisions the MTHI and MTLO instructions are only
really useful for context switches as data placed there cannot be further
used, except to read it back with MFHI or MFLO. Consequently MTHI and
MTLO are seldom used and those architecture revisions do not have hardware
interlocks implemented for them, requiring a sufficient number of other
instructions to be executed between a MFHI or MFLO and a following MTHI or
MTLO for predictable results to be produced. Otherwise the MTHI/MTLO
operation may (and generally will) corrupt data retrieved with MFHI/MFLO.
NB later architecture revisions have integer multiply-accumulate
instructions which use HI/LO as one of inputs, making MTHI and MTLO more
useful, and they do implement hardware interlocks for them.
So the message above means that the result of a MFHI or MFLO operation
(MF) at 0x88015698 executed after an MD unit operation (OP) at 0x88000464
has been corrupted by a MTHI or MTLO operation (MT) at 0x88003c68. And I
believe that what I wrote above makes the HILO and MFHI prefixes obvious.
HTH,
Maciej