From: Simon Marchi <simon.marchi@efficios.com>
Date: Mon, 18 Dec 2023 20:02:46 +0000 (-0500)
Subject: gdb: remove stale comment in value_assign
X-Git-Tag: binutils-2_42~500
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f00c5474efae435e6680afa86a075cd212222ebe;p=thirdparty%2Fbinutils-gdb.git

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 <tom@tromey.com>
---

diff --git a/gdb/valops.c b/gdb/valops.c
index 21b010684af..049314cf7db 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);