diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2020-05-27 11:13:59 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2020-05-27 11:15:56 -0400 |
| commit | 64874a40306f556c290c8829f42526443db0f9e9 (patch) | |
| tree | 9abf010f6792d431c14713c6d07fab342c9684ba /gdb/compile | |
| parent | 4ab09049d65fbda8637400bde3d39761ae512404 (diff) | |
| download | gdb-64874a40306f556c290c8829f42526443db0f9e9.zip gdb-64874a40306f556c290c8829f42526443db0f9e9.tar.gz gdb-64874a40306f556c290c8829f42526443db0f9e9.tar.bz2 | |
Remove reference to dwarf2_per_cu_data::dwarf2_per_objfile in queue_and_load_all_dwo_tus
In this context, we know that per_cu->cu will be set, as there is this
assertion:
gdb_assert (per_cu->cu != NULL)
So in order to remove the dwarf2_per_cu_data::dwarf2_per_objfile
reference in queue_and_load_all_dwo_tus, we can go through per_cu->cu.
This adds a reference to dwarf2_per_cu_data::cu, but it will get removed
eventually, in a subsequent patch.
gdb/ChangeLog:
* dwarf2/read.c (queue_and_load_all_dwo_tus): Access per_objfile
data through per_cu->cu.
Change-Id: Id4662828ac3c5bc93fe221df3c9bd9a36a8427ad
Diffstat (limited to 'gdb/compile')
0 files changed, 0 insertions, 0 deletions