aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/py-linetable.c
diff options
context:
space:
mode:
authorZoran Zaric <zoran.zaric@amd.com>2020-09-15 12:35:56 +0100
committerZoran Zaric <zoran.zaric@amd.com>2021-08-05 16:40:26 +0100
commitf9e4ed8baa9eeebc71be88f863c52f81e42bed34 (patch)
treefae4b1fd02894866edb1fd00402028afb5b7ca4b /gdb/python/py-linetable.c
parent14a62404c9845827d92986af2dfcdbb7e48c65fc (diff)
downloadbinutils-f9e4ed8baa9eeebc71be88f863c52f81e42bed34.zip
binutils-f9e4ed8baa9eeebc71be88f863c52f81e42bed34.tar.gz
binutils-f9e4ed8baa9eeebc71be88f863c52f81e42bed34.tar.bz2
Merge evaluate_for_locexpr_baton evaluator
The evaluate_for_locexpr_baton is the last derived class from the dwarf_expr_context class. It's purpose is to support the passed in buffer functionality. Although, it is not really necessary to merge this class with it's base class, doing that simplifies new expression evaluator design. Considering that this functionality is going around the DWARF standard, it is also reasonable to expect that with a new evaluator design and extending the push object address functionality to accept any location description, there will be no need to support passed in buffers. Alternatively, it would also makes sense to abstract the interaction between the evaluator and a given resource in the near future. The passed in buffer would then be a specialization of that abstraction. gdb/ChangeLog: * dwarf2/expr.c (dwarf_expr_context::read_mem): Merge with evaluate_for_locexpr_baton implementation. * dwarf2/loc.c (class evaluate_for_locexpr_baton): Remove class. (evaluate_for_locexpr_baton::read_mem): Move to dwarf_expr_context. (dwarf2_locexpr_baton_eval): Instantiate dwarf_expr_context instead of evaluate_for_locexpr_baton class.
Diffstat (limited to 'gdb/python/py-linetable.c')
0 files changed, 0 insertions, 0 deletions