From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA/PATCH/mips16] Remove dead code in mips_insn16_frame_cache
Date: Thu, 23 Sep 2004 23:34:00 -0000 [thread overview]
Message-ID: <20040923233443.GJ968@gnat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
I think this is obvious, but just in case, I'm posting this as a
semi-rfa before I do something wrong.
2004-09-23 Joel Brobecker <brobecker@gnat.com>
* mips-tdep.c (mips_insn16_frame_cache): Remove dead code or
conditions that will always be true.
Untested. I'll make sure it compiles before I commit.
OK to apply anyway?
The next step is to mimick the mips32 changes to mips16, so that they
both update the frame cache.
Thanks,
--
Joel
[-- Attachment #2: mips16.diff --]
[-- Type: text/plain, Size: 1708 bytes --]
Index: mips-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mips-tdep.c,v
retrieving revision 1.324
diff -u -p -r1.324 mips-tdep.c
--- mips-tdep.c 16 Sep 2004 00:35:55 -0000 1.324
+++ mips-tdep.c 23 Sep 2004 23:23:16 -0000
@@ -1850,24 +1850,14 @@ mips_insn16_frame_cache (struct frame_in
/* If the address is odd, assume this is MIPS16 code. */
addr = PROC_LOW_ADDR (proc_desc);
- mips16 = pc_is_mips16 (addr);
/* Scan through this function's instructions preceding the
current PC, and look for those that save registers. */
while (addr < frame_pc_unwind (next_frame))
{
- if (mips16)
- {
- mips16_decode_reg_save (mips16_fetch_instruction (addr),
- &gen_save_found);
- addr += MIPS16_INSTLEN;
- }
- else
- {
- mips32_decode_reg_save (mips32_fetch_instruction (addr),
- &gen_save_found, &float_save_found);
- addr += MIPS_INSTLEN;
- }
+ mips16_decode_reg_save (mips16_fetch_instruction (addr),
+ &gen_save_found);
+ addr += MIPS16_INSTLEN;
}
gen_mask = gen_save_found;
float_mask = float_save_found;
@@ -1891,7 +1881,6 @@ mips_insn16_frame_cache (struct frame_in
order of that normally used by gcc. Therefore, we have to fetch
the first instruction of the function, and if it's an entry
instruction that saves $s0 or $s1, correct their saved addresses. */
- if (pc_is_mips16 (PROC_LOW_ADDR (proc_desc)))
{
ULONGEST inst = mips16_fetch_instruction (PROC_LOW_ADDR (proc_desc));
if ((inst & 0xf81f) == 0xe809 && (inst & 0x700) != 0x700)
next reply other threads:[~2004-09-23 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 23:34 Joel Brobecker [this message]
2004-09-24 14:19 ` Andrew Cagney
2004-09-24 14:35 ` Joel Brobecker
2004-09-24 15:12 ` Andrew Cagney
2004-10-01 0:21 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040923233443.GJ968@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox