This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [2/2] Reducing the overhead of dwarf2 location tracking
- From: Richard Sandiford <richard dot sandiford at linaro dot org>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, patches at linaro dot org
- Date: Mon, 04 Apr 2011 11:49:24 +0100
- Subject: Re: [2/2] Reducing the overhead of dwarf2 location tracking
- References: <g4aahbvviw.fsf@linaro.org> <20110304152205.GH30899@tyan-ft48-01.lab.bos.redhat.com> <87mxl9vdj0.fsf@firetop.home>
Richard Sandiford <rdsandiford@googlemail.com> writes:
> gcc/
> * dwarf2out.c (dw_loc_list_node): Add resolved_addr and replaced.
> (cached_dw_loc_list_def): New structure.
> (cached_dw_loc_list): New typedef.
> (cached_dw_loc_list_table): New variable.
> (cached_dw_loc_list_table_hash): New function.
> (cached_dw_loc_list_table_eq): Likewise.
> (add_location_or_const_value_attribute): Take a bool cache_p.
> Cache the list when the parameter is true.
> (gen_formal_parameter_die): Update caller.
> (gen_variable_die): Likewise.
> (dwarf2out_finish): Likewise.
> (dwarf2out_abstract_function): Nullify cached_dw_loc_list_table
> while generating debug info for the decl.
> (dwarf2out_function_decl): Clear cached_dw_loc_list_table.
> (dwarf2out_init): Initialize cached_dw_loc_list_table.
> (resolve_addr): Cache the result of resolving a chain of
> location lists.
This has been on mainline for a week without any reported problems (AFAIK).
Is it OK for 4.5 and 4.6 as well?
Thanks,
Richard