From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: Re: [rfa/dwarf/doc] Inter-compilation-unit reference support for partial DIEs
Date: Mon, 20 Sep 2004 16:41:00 -0000 [thread overview]
Message-ID: <20040920164124.GA23738@nevyn.them.org> (raw)
In-Reply-To: <20040916211543.GA28956@nevyn.them.org>
On Thu, Sep 16, 2004 at 05:15:43PM -0400, Daniel Jacobowitz wrote:
> Doc changes already approved. Dwarf changes reposted with all
> of Jim's feedback incorporated, as far as I can tell. Tested
> i386-pc-linux-gnu, no regressions.
>
> Jim, did I get everything? Does it look OK now?
Ping?
>
> --
> Daniel Jacobowitz
>
> 2004-09-16 Daniel Jacobowitz <dan@debian.org>
>
> * Makefile.in (dwarf2read.o): Update dependencies.
> * dwarf2read.c: Include "command.h" and "gdbcmd.h".
> (struct dwarf2_per_objfile): Add all_comp_units, n_comp_units,
> and read_in_chain.
> (struct dwarf2_cu): Add read_in_chain, per_cu, last_used,
> mark, and has_form_ref_addr.
> (struct dwarf2_per_cu_data): New.
> (dwarf2_max_cache_age): New.
> (dwarf2_build_psymtabs_hard): Free cached compilation units
> after loading. Create and manage the list of compilation units.
> Remove unnecessary NULL initialization. Fix indentation.
> (psymtab_to_symtab_1): Initialize all of CU.
> (dwarf2_read_abbrevs): Set has_form_ref_addr.
> (find_partial_die): Use dwarf2_find_containing_comp_unit
> and load_comp_unit.
> (free_stack_comp_unit): Update comments. Clear the per-cu
> pointer. Handle aging.
> (dwarf2_find_containing_comp_unit, free_cached_comp_units)
> (age_cached_comp_units, free_one_cached_comp_unit)
> (dwarf2_mark, dwarf2_clear_marks, create_all_comp_units)
> (load_comp_unit, dwarf2_find_comp_unit, free_one_comp_unit)
> (set_dwarf2_cmdlist, show_dwarf2_cmdlist, set_dwarf2_cmd)
> (show_dwarf2_cmd): New.
> (_initialize_dwarf2_read): Provide "maint set dwarf2 max-cache-age"
> and "maint show dwarf2 max-cache-age".
> * gdbcmd.h (maintenance_set_cmdlist, maintenance_show_cmdlist): New
> externs.
> * maint.c (maintenance_set_cmdlist, maintenance_show_cmdlist): Make
> global.
>
> 2004-09-16 Daniel Jacobowitz <dan@debian.org>
>
> * gdb.texinfo (Maintenance Commands): Document "maint set dwarf2
> max-cache-age" and "maint show dwarf2 max-cache-age".
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-09-20 16:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 17:09 Daniel Jacobowitz
2004-04-20 19:43 ` Eli Zaretskii
2004-04-22 22:15 ` Jim Blandy
2004-06-17 3:42 ` Daniel Jacobowitz
2004-06-17 4:19 ` Eli Zaretskii
2004-06-17 4:21 ` Daniel Jacobowitz
2004-06-17 4:26 ` Eli Zaretskii
2004-07-15 18:45 ` Daniel Jacobowitz
2004-07-16 11:18 ` Eli Zaretskii
2004-08-04 23:07 ` Daniel Jacobowitz
2004-08-05 17:23 ` Jim Blandy
2004-08-05 18:05 ` Daniel Jacobowitz
2004-08-06 22:25 ` Jim Blandy
2004-08-07 22:01 ` Daniel Jacobowitz
2004-08-08 4:42 ` Jim Blandy
2004-08-08 18:17 ` Daniel Jacobowitz
2004-08-08 19:30 ` Daniel Jacobowitz
2004-08-10 0:24 ` Jim Blandy
2004-08-06 22:28 ` Jim Blandy
2004-08-06 22:58 ` Jim Blandy
2004-08-07 0:05 ` Jim Blandy
2004-09-16 21:15 ` Daniel Jacobowitz
2004-09-20 16:41 ` Daniel Jacobowitz [this message]
2004-09-20 20:28 ` Jim Blandy
2004-09-20 23:59 ` Daniel Jacobowitz
2004-04-22 22:58 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040920164124.GA23738@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox