From 3b57368f67433a95492ab4b40033cde3000f1dd8 Mon Sep 17 00:00:00 2001 From: "hp.com!davidm" Date: Tue, 31 Aug 2004 13:59:10 +0000 Subject: [PATCH] (struct cursor): Clarify meaning of "rbs_curr" member. (Logical change 1.259) --- include/tdep-ia64.h | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/include/tdep-ia64.h b/include/tdep-ia64.h index 9bf027d6..0a3bec75 100644 --- a/include/tdep-ia64.h +++ b/include/tdep-ia64.h @@ -157,7 +157,15 @@ struct cursor current frame may be backed up. Since there are at most 96 stacked registers and since we only have to track the current frame and only areas that are not empty, this puts an upper - limit on the # of backing-store areas we have to track. */ + limit on the # of backing-store areas we have to track. + + Note that the rbs-area indexed by rbs_curr identifies the + rbs-area that was in effect at the time AR.BSP had the value + c->bsp. However, this rbs area may not actually contain the + value in the register that c->bsp corresponds to because that + register may not have gotten spilled until much later, when a + possibly different rbs-area might have been in effect + already. */ uint8_t rbs_curr; /* index of curr. rbs-area (contains c->bsp) */ uint8_t rbs_left_edge; /* index of inner-most valid rbs-area */ struct rbs_area