[PATCH 0/3] regnum and next_frame_id are only used for lval_register

[Yao Qi <qiyaoltc at gmail dot com>]

This patch series changes 'struct value' fields regnum and next_frame_id
are only used for lval_register.  This patch series is from the discussion
https://sourceware.org/ml/gdb-patches/2016-11/msg00630.html

Nowadays, computed value still uses next_frame_id, which is a misuse or abuse
to me.  Patch #1 adds a frame id in piece_closure, so computed value can get
frame id there.  Patch #2 moves fields regnum and next_frame_id to
value.location.  Then, value.location.address is only used by lval_memory,
patch #3 restrict the checking on using address.

Regression tested on x86_64-linux.

*** BLURB HERE ***

Yao Qi (3):
  Move computed value's frame id to piece_closure
  Adjust Value.location for lval_register
  Restrict checking value.lval on using address

 gdb/ada-lang.c  |  2 +-
 gdb/dwarf2loc.c | 25 ++++++++++++-------------
 gdb/elfread.c   |  2 ++
 gdb/valops.c    |  1 -
 gdb/value.c     | 57 +++++++++++++++++++++------------------------------------
 5 files changed, 36 insertions(+), 51 deletions(-)

-- 
1.9.1