gdb, dwarf: move part of dwarf2_get_pc_bounds into separate function
authorNils-Christian Kempke <nils-christian.kempke@intel.com>
Wed, 13 Jul 2022 08:57:27 +0000 (10:57 +0200)
committerIjaz, Abdul B <abdul.b.ijaz@intel.com>
Fri, 29 Dec 2023 10:28:35 +0000 (11:28 +0100)
commit69570475c6142c656640106ff0f6ff13c20ae621
treeb2b3d2f52fd42b69054dc56ec1d49a9c77d4c635
parent90827b4eefb06f6e0ab6cbac9eb94922e2cc8aee
gdb, dwarf: move part of dwarf2_get_pc_bounds into separate function

This commit is in preparation of the next commit.  There, we will add
a second variation to retrieve the pc bounds for DIEs tagged with
DW_TAG_entry_point.  Instead of dwarf_get_pc_bounds_ranges_or_highlow_pc
we will call a separate method for entry points.  As the validity checks
at the endo f dwarf2_get_pc_bounds are the same for both variants,
we introduced the new dwarf_get_pc_bounds_ranges_or_highlow_pc method,
outsourcing part of dwarf2_get_pc_bounds.

This commit should have no functional impact on GDB.

Approved-by: Tom Tromey <tom@tromey.com>
gdb/dwarf2/read.c