aboutsummaryrefslogtreecommitdiff
path: root/gcc/config/d30v
diff options
context:
space:
mode:
authorAndreas Jaeger <aj@gcc.gnu.org>2003-05-31 20:45:31 +0200
committerAndreas Jaeger <aj@gcc.gnu.org>2003-05-31 20:45:31 +0200
commit0d569849e6a8c783c2e2331417e85c3a40a3b980 (patch)
treee51a63762d9808d04eaa7cef419df116b60f75da /gcc/config/d30v
parentc79af3fafd7f53e110ae9286f221032cd11a1ac6 (diff)
downloadgcc-0d569849e6a8c783c2e2331417e85c3a40a3b980.zip
gcc-0d569849e6a8c783c2e2331417e85c3a40a3b980.tar.gz
gcc-0d569849e6a8c783c2e2331417e85c3a40a3b980.tar.bz2
function.c (trampoline_address): Remove ALLOCATE_TRAMPOLINE usage.
* function.c (trampoline_address): Remove ALLOCATE_TRAMPOLINE usage. * doc/tm.texi (Trampolines): Remove ALLOCATE_TRAMPOLINE. * config/d30v/d30v.h: Remove traces of ALLOCATE_TRAMPOLINE. * system.h: Poison ALLOCATE_TRAMPOLINE. * doc/tm.texi (Misc): Remove HANDLE_PRAGMA. * system.h: Poison HANDLE_PRAGMA. In f/ * lex.c (ffelex_hash_): Remove HANDLE_PRAGMA and HANDLE_GENERIC_PRAGMA dependend code, remove #if 0 code. (pragma_getc): Removed. (pragma_ungetc): Removed. From-SVN: r67274
Diffstat (limited to 'gcc/config/d30v')
-rw-r--r--gcc/config/d30v/d30v.h21
1 files changed, 1 insertions, 20 deletions
diff --git a/gcc/config/d30v/d30v.h b/gcc/config/d30v/d30v.h
index 05b2e0c..57a90fe 100644
--- a/gcc/config/d30v/d30v.h
+++ b/gcc/config/d30v/d30v.h
@@ -1,5 +1,5 @@
/* Definitions of target machine for Mitsubishi D30V.
- Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002
+ Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002, 2003
Free Software Foundation, Inc.
Contributed by Cygnus Solutions.
@@ -2024,25 +2024,6 @@ typedef struct machine_function GTY(())
#define INITIALIZE_TRAMPOLINE(ADDR, FNADDR, STATIC_CHAIN) \
d30v_initialize_trampoline (ADDR, FNADDR, STATIC_CHAIN)
-/* A C expression to allocate run-time space for a trampoline. The expression
- value should be an RTX representing a memory reference to the space for the
- trampoline.
-
- If this macro is not defined, by default the trampoline is allocated as a
- stack slot. This default is right for most machines. The exceptions are
- machines where it is impossible to execute instructions in the stack area.
- On such machines, you may have to implement a separate stack, using this
- macro in conjunction with output_function_prologue () and
- output_function_epilogue ().
-
- FP points to a data structure, a `struct function', which describes the
- compilation status of the immediate containing function of the function
- which the trampoline is for. Normally (when `ALLOCATE_TRAMPOLINE' is not
- defined), the stack slot for the trampoline is in the stack frame of this
- containing function. Other allocation strategies probably must do something
- analogous with this information. */
-/* #define ALLOCATE_TRAMPOLINE(FP) */
-
/* Implementing trampolines is difficult on many machines because they have
separate instruction and data caches. Writing into a stack location fails
to clear the memory in the instruction cache, so when the program jumps to