aboutsummaryrefslogtreecommitdiff
path: root/gdb/ada-lang.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@efficios.com>2025-03-05 16:10:07 -0500
committerSimon Marchi <simon.marchi@polymtl.ca>2025-03-06 11:39:00 -0500
commit54333345d29d85d61bd7a00e9e557d857795122f (patch)
treec0fce466715ad0e4d488d3af01866ec01abb0a06 /gdb/ada-lang.c
parente9c7a913187be220ed6a61e646ff1f6ed5f1e05a (diff)
downloadbinutils-54333345d29d85d61bd7a00e9e557d857795122f.zip
binutils-54333345d29d85d61bd7a00e9e557d857795122f.tar.gz
binutils-54333345d29d85d61bd7a00e9e557d857795122f.tar.bz2
gdb/dwarf: move a bunch of DIE-reading functions to cutu_reader
With the hope of organizing things better and spotting patterns that could lead to simplification, move all these functions to be methods of cutu_reader. At least, this gives a good picture of what the entry points for DIE and attribute reading are, by looking at what methods are public. Right now, my vague understanding of cutu_reader is that it does 3 things: - it provides means to navigate and read the DIE tree, abstracting things like whether the real content is in a DWO file or not - it builds a dwarf2_cu object, for its own use but also for the use of the caller - it fills in missing details in the passed in dwarf2_per_cu In the future, I'd like to separate those concerns. I think that cutu_reader could retain the first one of those concerns, while the other two could be done by other classes or functions, perhaps using cutu_reader under the hood. Change-Id: I04e0d6c864bbc09c7071ac8e9493e1e54c093d68 Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/ada-lang.c')
0 files changed, 0 insertions, 0 deletions