From 1aee363c16e15b48e09ddb17f7aa4d007f80fbe7 Mon Sep 17 00:00:00 2001 From: "Maciej W. Rozycki" Date: Wed, 26 Jun 2013 15:10:33 +0000 Subject: [PATCH] * mips-tdep.c (mips_next_pc): Fix a typo. --- gdb/ChangeLog | 4 ++++ gdb/mips-tdep.c | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index fd7a3f23319..e2ffd230025 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2013-06-26 Maciej W. Rozycki + + * mips-tdep.c (mips_next_pc): Fix a typo. + 2013-06-26 Maciej W. Rozycki * mips-tdep.c (micromips_scan_prologue): Fix a typo. diff --git a/gdb/mips-tdep.c b/gdb/mips-tdep.c index 66fd562024e..74f27bc7e67 100644 --- a/gdb/mips-tdep.c +++ b/gdb/mips-tdep.c @@ -2242,7 +2242,7 @@ mips16_next_pc (struct frame_info *frame, CORE_ADDR pc) /* The mips_next_pc function supports single_step when the remote target monitor or stub is not developed enough to do a single_step. It works by decoding the current instruction and predicting where a - branch will go. This isnt hard because all the data is available. + branch will go. This isn't hard because all the data is available. The MIPS32, MIPS16 and microMIPS variants are quite different. */ static CORE_ADDR mips_next_pc (struct frame_info *frame, CORE_ADDR pc) -- 2.30.2