This is an trivial patch. I found this when looking at AVR32 target code.

Jie
From 30dc90988489f91c5599ee5af515d0574d4f7577 Mon Sep 17 00:00:00 2001
From: Jie Zhang <jie.zh...@analog.com>
Date: Tue, 3 May 2011 14:43:22 -0400
Subject: [PATCH] Remove useless MIPS code in avr32_ap7k.c.

---
 src/target/avr32_ap7k.c |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/src/target/avr32_ap7k.c b/src/target/avr32_ap7k.c
index 70e5129..afac664 100644
--- a/src/target/avr32_ap7k.c
+++ b/src/target/avr32_ap7k.c
@@ -110,7 +110,6 @@ int avr32_ap7k_restore_context(struct target *target)
 static int avr32_read_core_reg(struct target *target, int num)
 {
 	uint32_t reg_value;
-	struct avr32_core_reg *mips_core_reg;
 
 	/* get pointers to arch-specific information */
 	struct avr32_ap7k_common *ap7k = target_to_ap7k(target);
@@ -118,7 +117,6 @@ static int avr32_read_core_reg(struct target *target, int num)
 	if ((num < 0) || (num >= AVR32NUMCOREREGS))
 		return ERROR_INVALID_ARGUMENTS;
 
-	mips_core_reg = ap7k->core_cache->reg_list[num].arch_info;
 	reg_value = ap7k->core_regs[num];
 	buf_set_u32(ap7k->core_cache->reg_list[num].value, 0, 32, reg_value);
 	ap7k->core_cache->reg_list[num].valid = 1;
@@ -130,7 +128,6 @@ static int avr32_read_core_reg(struct target *target, int num)
 static int avr32_write_core_reg(struct target *target, int num)
 {
 	uint32_t reg_value;
-	struct avr32_core_reg *mips_core_reg;
 
 	/* get pointers to arch-specific information */
 	struct avr32_ap7k_common *ap7k = target_to_ap7k(target);
@@ -139,7 +136,6 @@ static int avr32_write_core_reg(struct target *target, int num)
 		return ERROR_INVALID_ARGUMENTS;
 
 	reg_value = buf_get_u32(ap7k->core_cache->reg_list[num].value, 0, 32);
-	mips_core_reg = ap7k->core_cache->reg_list[num].arch_info;
 	ap7k->core_regs[num] = reg_value;
 	LOG_DEBUG("write core reg %i value 0x%" PRIx32 "", num , reg_value);
 	ap7k->core_cache->reg_list[num].valid = 1;
-- 
1.7.2.5

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to