From c465f4303776f6609f1ca4835b4bf3627e7c61af Mon Sep 17 00:00:00 2001 From: Simon Marchi Date: Thu, 21 Dec 2023 16:28:19 +0000 Subject: gdb: remove read_frame_register_value's frame parameter By now, all register struct values should have a valid next frame id (assuming they are created using value::allocate_register or value::allocate_register_lazy), so there should be no need to pass a frame alongside the value to read_frame_register_value. Remove the frame parameter and adjust read_frame_register_value accordingly. While at it, make read_frame_register_value static, it's only used in findvar.c. Change-Id: I118959ef8c628499297c67810916e8ba9934bfac --- gdb/value.h | 3 --- 1 file changed, 3 deletions(-) (limited to 'gdb/value.h') diff --git a/gdb/value.h b/gdb/value.h index 86ad3ff..c56504b 100644 --- a/gdb/value.h +++ b/gdb/value.h @@ -1119,9 +1119,6 @@ extern value *default_value_from_register (gdbarch *gdbarch, type *type, int regnum, const frame_info_ptr &this_frame); -extern void read_frame_register_value (struct value *value, - frame_info_ptr frame); - extern struct value *value_from_register (struct type *type, int regnum, frame_info_ptr frame); -- cgit v1.1