From 82d1552e979875fc6e25a31800322b46c1dfe02e Mon Sep 17 00:00:00 2001 From: Ulrich Weigand Date: Mon, 18 Jun 2007 18:28:29 +0000 Subject: 2007-06-18 Markus Deuling * gdbarch.sh (EXTRACT_RETURN_VALUE): Replace with gdbarch_extract_return_value. * value.c (generic_use_struct_convention): Likewise (comment). * ia64-tdep.c (ia64_use_struct_convention): Likewise (comment). * arch-utils.c (legacy_return_value): Likewise. * arch-utils.h (legacy_return_value): Likewise (comment). * gdbarch.sh (STORE_RETURN_VALUE): Replace by gdbarch_store_return_value. * stack.c (return_command): Likewise (comment). * arch-utils.h (legacy_return_value): Likewise (comment). * arch-utils.c (legacy_return_value): Likewise. * gdbarch.c, gdbarch.h: Regenerate. --- gdb/value.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gdb/value.c') diff --git a/gdb/value.c b/gdb/value.c index 7404408..52ba2ed 100644 --- a/gdb/value.c +++ b/gdb/value.c @@ -1654,7 +1654,7 @@ coerce_enum (struct value *arg) /* Should we use DEPRECATED_EXTRACT_STRUCT_VALUE_ADDRESS instead of - EXTRACT_RETURN_VALUE? GCC_P is true if compiled with gcc and TYPE + gdbarch_extract_return_value? GCC_P is true if compiled with gcc and TYPE is the type (which is known to be struct, union or array). On most machines, the struct convention is used unless we are -- cgit v1.1