summaryrefslogtreecommitdiff
path: root/gdb/i960-tdep.c
diff options
context:
space:
mode:
authorKevin Buettner <kevinb@redhat.com>2000-05-28 01:12:42 +0000
committerKevin Buettner <kevinb@redhat.com>2000-05-28 01:12:42 +0000
commitbf6c959448e3470b740fc6f032faf4ee6c1ed43a (patch)
tree8aeacca23eb32d57e7ef9abce8d272f5b3adc53c /gdb/i960-tdep.c
parentb25fcc020b2d009c63e29b7655a7534507a50f88 (diff)
downloadgdb-bf6c959448e3470b740fc6f032faf4ee6c1ed43a.tar.gz
Diffstat (limited to 'gdb/i960-tdep.c')
-rw-r--r--gdb/i960-tdep.c5
1 files changed, 2 insertions, 3 deletions
diff --git a/gdb/i960-tdep.c b/gdb/i960-tdep.c
index eff41361a5f..f7aab5fb8c4 100644
--- a/gdb/i960-tdep.c
+++ b/gdb/i960-tdep.c
@@ -29,9 +29,8 @@
#include "gdbcore.h"
#include "inferior.h"
-static CORE_ADDR next_insn PARAMS ((CORE_ADDR memaddr,
- unsigned int *pword1,
- unsigned int *pword2));
+static CORE_ADDR next_insn (CORE_ADDR memaddr,
+ unsigned int *pword1, unsigned int *pword2);
/* Does the specified function use the "struct returning" convention
or the "value returning" convention? The "value returning" convention