[ARM] Store exception handling information per-bfd instead of per-objfile
authorLuis Machado <luis.machado@linaro.org>
Thu, 31 Oct 2019 19:30:44 +0000 (16:30 -0300)
committerLuis Machado <luis.machado@linaro.org>
Thu, 31 Oct 2019 19:30:44 +0000 (16:30 -0300)
commita2726d4ff80168a8134c68cb798e3f5f537b0eba
tree512800576a989ce7797d8cba2c664752638d8392
parent75cafaa61a0244016a2c2ee1d0b2742d674d7373
[ARM] Store exception handling information per-bfd instead of per-objfile

Based on feedback from Tromey, update the use of objfile_key in gdb/arm-tdep.c
to use bfd_key instead. That way we don't have to re-create the exception
handling data all over again if it was done before for the same BFD.

gdb/ChangeLog:

2019-10-31  Luis Machado  <luis.machado@linaro.org>

* arm-tdep.c (arm_exidx_data_key): Use bfd_key instead of
objfile_key.
(arm_exidx_new_objfile): Adjust to use objfile->obfd instead of
objfile to fetch per-bfd data.
(arm_find_exidx_entry): Likewise.

Change-Id: Ia7b3208ea8d788414600fa6d770ac76db0562859
gdb/ChangeLog
gdb/arm-tdep.c