From f00c5474efae435e6680afa86a075cd212222ebe Mon Sep 17 00:00:00 2001 From: Simon Marchi Date: Mon, 18 Dec 2023 15:02:46 -0500 Subject: gdb: remove stale comment in value_assign This comment is no longer relevant, put_frame_register_bytes now accepts the "next frame". Change-Id: I077933a03f8bdb886f8ba10a98d1202a38bce0a9 Approved-By: Tom Tromey --- gdb/valops.c | 7 ------- 1 file changed, 7 deletions(-) diff --git a/gdb/valops.c b/gdb/valops.c index 21b0106..049314c 100644 --- a/gdb/valops.c +++ b/gdb/valops.c @@ -1193,13 +1193,6 @@ value_assign (struct value *toval, struct value *fromval) case lval_register: { - /* Figure out which frame this register value is in. The value - holds the frame_id for the next frame, that is the frame this - register value was unwound from. - - Below we will call put_frame_register_bytes which requires that - we pass it the actual frame in which the register value is - valid, i.e. not the next frame. */ frame_info_ptr next_frame = frame_find_by_id (VALUE_NEXT_FRAME_ID (toval)); int value_reg = VALUE_REGNUM (toval); -- cgit v1.1