Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	Eli Zaretskii <eliz@elta.co.il>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFC/dwarf-2] Add support for included files
Date: Thu, 29 Apr 2004 23:32:00 -0000	[thread overview]
Message-ID: <vt24qr2nz4j.fsf@zenia.home> (raw)
In-Reply-To: <20040416230825.GK22414@gnat.com>


Joel Brobecker <brobecker@gnat.com> writes:
> Here is an updated version of the previous patch, adapted to fit in
> the current dwarf2read.c after Daniel's changes, and with comments
> added. It's actually slightly smaller thanks to Daniel's changes
> :-).

Great!

I actually have still more comments:

- Rather than passing 'line_offset' by reference to read_partial_die,
  could you add a line_offset field to 'struct partial_die_info, and have
  read_partial_die set that?  That would seem more consistent with the
  rest of what read_partial_die does.  Then
  'dwarf2_build_include_psymtabs' should take a pointer to the CU die.

  That's assuming Daniel doesn't see any problem enlarging
  partial_die_info.  If he does, maybe we could add the fields to
  'struct dwarf2_cu' instead: it's a little odd to have
  'read_partial_die' set the cu's fields directly, but not horribly
  so, as long as the die's tag is DW_TAG_compile_unit.

- Is it really okay to pass NULL to dwarf_decode_lines for comp_dir?
  Won't the filenames of the partial symbol tables be different from
  those of the symbol tables?  To fix this, read_partial_die would
  have to check for DW_AT_comp_dir attributes, too.

- It seems to me the file_is_included array should be in struct
  line_header, with add_file_name managing its allocation /
  initialization in parallel with file_names.  It's already the case
  that that structure is mutated by the act of processing the line
  number program, so I don't see that it's a serious change to the
  usage patterns of that structure type.

- I'd rather see the call to dwarf2_build_include_psymtabs before the
  assignment to info_ptr, not after.  Not that it matters much.

- Thanks for fixing the comments on dwarf_decode_lines --- especially
  the references to arguments that had been missing for some time now.


  reply	other threads:[~2004-04-29 23:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 16:05 Jim Blandy
2004-04-13  5:20 ` Joel Brobecker
2004-04-14 19:10   ` Jim Blandy
2004-04-15 22:13     ` Joel Brobecker
2004-04-16  4:24       ` Jim Blandy
2004-04-16  4:28         ` Joel Brobecker
2004-04-16 23:08         ` Joel Brobecker
2004-04-29 23:32           ` Jim Blandy [this message]
2004-05-01  1:14             ` Joel Brobecker
2004-05-01  4:57               ` Jim Blandy
2004-05-03 16:25                 ` Joel Brobecker
  -- strict thread matches above, loose matches on Subject: below --
2004-05-03 22:15 Andrew Pinski
2004-05-04  0:15 ` Joel Brobecker
2004-05-04  0:18   ` Andrew Pinski
2004-01-02  7:25 Joel Brobecker
2004-01-02 14:18 ` Daniel Jacobowitz
2004-01-03 14:42   ` Joel Brobecker
2004-01-03 16:34     ` Eli Zaretskii
2004-01-03 17:47       ` Joel Brobecker
2004-01-02 14:45 ` Eli Zaretskii
2004-01-05 16:18 ` Andrew Cagney
2004-01-05 19:17   ` Joel Brobecker

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=vt24qr2nz4j.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=brobecker@gnat.com \
    --cc=drow@mvista.com \
    --cc=eliz@elta.co.il \
    --cc=gdb-patches@sources.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