Run gdb/contrib/spellcheck.sh on directory sim.
Fix these todos:
...
TODO: inbetween -> between, in between, in-between
TODO: behavour -> behavior, behaviour
TODO: firts -> flirts, first
TODO: wich -> which, witch
...
Tested by rebuilding on x86_64-linux.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-By: Tom Tromey <tom@tromey.com>
{
if (PSW_RP && PC == RPT_E)
{
- /* Note: The behavour of a branch instruction at RPT_E
+ /* Note: The behavior of a branch instruction at RPT_E
is implementation dependant, this simulator takes the
branch. Branching to RPT_E is valid, the instruction
must be executed before the loop is taken. */
- Breakpoint register (0x01f800c4, write-only)
- Watchpoint register (0x01f800c8, write-only)
- System fault status register (0x01f800a0, read-write)
-- Firts failing address register (0x01f800a4, read-write)
+- First failing address register (0x01f800a4, read-write)
1.5 Memory interface
The GDB load command loads an aout file into the simulator
memory with the data section starting directly after the text
-section regardless of wich start address was specified for the data
+section regardless of which start address was specified for the data
at link time! This means that your applications either has to include
a routine that initialise the data segment at the proper address or
link with the data placed directly after the text section.
restart. (or to put it another way, long jump). In looking at the
code it may occure to you that, for some interrupts, they could
return instead of restarting the cpu (eg system_call). While true
- (it once was like that) I've decided to make the behavour of all
+ (it once was like that) I've decided to make the behavior of all
interrupt routines roughly identical.
Because, a cpu's recorded state (ie what is in the cpu structure)
/* System-call emulation - for user code. Instead of trapping system
- calls to kernel mode, the simulator emulates the kernels behavour */
+ calls to kernel mode, the simulator emulates the kernels behavior */
INLINE_OS_EMUL\
(void) os_emul_system_call
instructions are added to the instruction table that when executed
call this emulation function. The instruction call emulator should
verify the address that the instruction appears before emulating
- the required behavour. If the verification fails, a zero value
+ the required behavior. If the verification fails, a zero value
should be returned (indicating instruction illegal). */
INLINE_OS_EMUL\
-# Test for mf{hi,lo} -> mult/div/mt{hi,lo} with 2 nops inbetween.
+# Test for mf{hi,lo} -> mult/div/mt{hi,lo} with 2 nops in between.
#
# mach: -mips32r6 -mips64r6 all
# as: -mabi=eabi
-# Test for mf{hi,lo} -> mult/div/mt{hi,lo} with 2 nops inbetween.
+# Test for mf{hi,lo} -> mult/div/mt{hi,lo} with 2 nops in between.
#
# mach: all
# as: -mabi=eabi -mmicromips