aboutsummaryrefslogtreecommitdiff
path: root/gdb/config
diff options
context:
space:
mode:
Diffstat (limited to 'gdb/config')
-rw-r--r--gdb/config/m32r/tm-m32r.h25
-rw-r--r--gdb/config/sh/tm-sh.h32
-rw-r--r--gdb/config/v850/tm-v850.h23
3 files changed, 2 insertions, 78 deletions
diff --git a/gdb/config/m32r/tm-m32r.h b/gdb/config/m32r/tm-m32r.h
index c9342e1..4e01197 100644
--- a/gdb/config/m32r/tm-m32r.h
+++ b/gdb/config/m32r/tm-m32r.h
@@ -222,7 +222,6 @@ extern CORE_ADDR m32r_push_arguments PARAMS ((int nargs,
one that takes account of generic CALL_DUMMY frames */
#define GET_SAVED_REGISTER
-#if 1
#define CALL_DUMMY {0}
#define CALL_DUMMY_LENGTH (0)
#define CALL_DUMMY_START_OFFSET (0)
@@ -230,27 +229,3 @@ extern CORE_ADDR m32r_push_arguments PARAMS ((int nargs,
#define FIX_CALL_DUMMY(DUMMY1, STARTADDR, FUNADDR, NARGS, ARGS, TYPE, GCCP)
#define CALL_DUMMY_LOCATION AT_ENTRY_POINT
#define CALL_DUMMY_ADDRESS() entry_point_address ()
-
-#else
-/*
-/* Use these defines if, for whatever reason, you want to use a
- genuine call_dummy sequence (A sequence of machine instructions
- that GDB will write into the target address space, usually on the
- stack, for calling a function in the inferior):
-
- This sequence of words defines the instructions:
-
- ld24 R8, <destination>
- jl R8
- nop
- trap
-*/
-#define CALL_DUMMY { 0xe8000000, 0x1ec87000, 0x10f110f1 }
-#define CALL_DUMMY_LENGTH (12)
-#define CALL_DUMMY_START_OFFSET (0)
-#define CALL_DUMMY_BREAKPOINT_OFFSET (8)
-#define FIX_CALL_DUMMY(DUMMY1, STARTADDR, FUNADDR, NARGS, ARGS, TYPE, GCCP) \
- m32r_fix_call_dummy (DUMMY1, STARTADDR, FUNADDR, NARGS, ARGS, TYPE, GCCP)
-#define CALL_DUMMY_LOCATION ON_STACK
-#define NEED_TEXT_START_END
-#endif
diff --git a/gdb/config/sh/tm-sh.h b/gdb/config/sh/tm-sh.h
index 5347d72..ce873e5 100644
--- a/gdb/config/sh/tm-sh.h
+++ b/gdb/config/sh/tm-sh.h
@@ -248,36 +248,6 @@ extern CORE_ADDR sh_push_arguments PARAMS ((int nargs,
unsigned char struct_return,
CORE_ADDR struct_addr));
-#if 0
-/* Use these defines if, for whatever reason, you want to use a
- genuine call_dummy sequence (A sequence of machine instructions
- that GDB will write into the target address space, usually on the
- stack, for calling a function in the inferior):
-
- This sequence of words defines the instructions:
-
- mov.w @(2,PC), R8
- jsr @R8
- nop
- trap
- <destination>
-
- Note that the destination address is actually written into a word
- 8 bytes after the start of the CALL_DUMMY. The first instruction
- loads it from here using PC-relative addressing. Note also the
- NOP that must follow the jsr instruction to fill up the delay slot.
-*/
-
-#define CALL_DUMMY { 0xd801480b, 0x0009c3c3, 0x32323232, }
-#define CALL_DUMMY_LENGTH (12)
-#define CALL_DUMMY_START_OFFSET (0)
-#define CALL_DUMMY_BREAKPOINT_OFFSET (6)
-#define FIX_CALL_DUMMY(DUMMY, STARTADDR, FUNADDR, NARGS, ARGS, TYPE, GCCP) \
- sh_fix_call_dummy(DUMMY, STARTADDR, FUNADDR, NARGS, ARGS, TYPE, GCCP)
-#define CALL_DUMMY_LOCATION ON_STACK
-
-#else /* These defines write NO instructions into the inferior process,
- and are therefore preferred because they make target calls faster. */
#define CALL_DUMMY {0}
#define CALL_DUMMY_LENGTH (0)
#define CALL_DUMMY_START_OFFSET (0)
@@ -287,7 +257,7 @@ extern CORE_ADDR sh_push_arguments PARAMS ((int nargs,
#define CALL_DUMMY_ADDRESS() entry_point_address ()
extern CORE_ADDR sh_push_return_address PARAMS ((CORE_ADDR, CORE_ADDR));
#define PUSH_RETURN_ADDRESS(PC, SP) sh_push_return_address (PC, SP)
-#endif
+
#define FRAME_CHAIN(FRAME) sh_frame_chain(FRAME)
#define PUSH_DUMMY_FRAME generic_push_dummy_frame ()
diff --git a/gdb/config/v850/tm-v850.h b/gdb/config/v850/tm-v850.h
index 1bc61c4..9164617 100644
--- a/gdb/config/v850/tm-v850.h
+++ b/gdb/config/v850/tm-v850.h
@@ -113,27 +113,6 @@ extern CORE_ADDR v850_skip_prologue PARAMS ((CORE_ADDR pc));
extern void v850_pop_frame PARAMS ((struct frame_info *frame));
#define POP_FRAME v850_pop_frame (get_current_frame ())
-#if 0
-/* Use these defines if, for whatever reason, you want to use a
- genuine call_dummy sequence (A sequence of machine instructions
- that GDB will write into the target address space, usually on the
- stack, for calling a function in the inferior):
-
- This sequence of words defines the instructions:
-
- jarl <offset24>, r31
- trap
-*/
-#define CALL_DUMMY { 0x0000ff80, 0xffffffff }
-#define CALL_DUMMY_LENGTH (8)
-#define CALL_DUMMY_START_OFFSET (0)
-#define CALL_DUMMY_BREAKPOINT_OFFSET (4)
-#define CALL_DUMMY_LOCATION ON_STACK
-#define FIX_CALL_DUMMY(DUMMY, START, FUNADDR, NARGS, ARGS, TYPE, GCCP) \
- v850_fix_call_dummy (DUMMY, START, FUNADDR, NARGS, ARGS, TYPE, GCCP);
-
-#else /* These defines write NO instructions into the inferior process,
- and are therefore preferred because they make target calls faster. */
#define CALL_DUMMY {0}
#define CALL_DUMMY_START_OFFSET (0)
#define CALL_DUMMY_BREAKPOINT_OFFSET (0)
@@ -142,7 +121,7 @@ extern void v850_pop_frame PARAMS ((struct frame_info *frame));
#define CALL_DUMMY_ADDRESS() entry_point_address ()
extern CORE_ADDR v850_push_return_address PARAMS ((CORE_ADDR, CORE_ADDR));
#define PUSH_RETURN_ADDRESS(PC, SP) v850_push_return_address (PC, SP)
-#endif
+
#define PUSH_DUMMY_FRAME generic_push_dummy_frame ()