Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 6/8] Types GC [the GC itself]
Date: Mon, 25 May 2009 20:56:00 -0000	[thread overview]
Message-ID: <83tz38sxzx.fsf@gnu.org> (raw)
In-Reply-To: <20090525080323.GF13323@host0.dyn.jankratochvil.net>

> Date: Mon, 25 May 2009 10:03:23 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> 
> gdb/doc/
> 2009-05-25  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* gdbint.texinfo (Symbol Handling): New menu.
> 	(Partial Symbol Tables, Object File Formats, Debugging File Formats)
> 	(Adding a New Symbol Reader to GDB): New nodes from existing sections.
> 	(Types): New node from existing section.  New anchor `Builtin Types'.
> 	(Memory Management for Symbol Files): New node from existing section.
> 	Move types to ...
> 	(Memory Management for Types): ... here, in a new node.
> 	* observer.texi (mark_used): New.

Thanks.  I have a few comments about this part.

> +@code{TYPE_OBJFILE} macro indicates the current memory owner of the type.

 "The @code{TYPE_OBJFILE} macro ..."

> +Non-@code{NULL} value indicates it is owned by an objfile (specifically by its

 "A non-@code{NULL} value indicates ..."

> +User convenience variables, et cetera, have associated types.  Normally these

Can you spell out what is behind the "et cetera" here?  If the full
list is too long, naming just the most frequently used ones would be
good enough.

> +Types with null @code{TYPE_OBJFILE} can be either permanent types
> +(@pxref{Builtin Types}) or reclaimable types which will be deallocated at the
> +first idle @value{GDBN} moment if the last object referencing them is removed
.

I think "the first idle GDB moment after the last object ... is
removed" is more accurate.  "After" instead of "if".

> +Permanent types are allocated by the function @code{alloc_type} (and its
> +derivations like @code{init_type}) specifying objfile as @code{NULL}.  The
> +reclaimable types are created the same way but moreover they need to have
                                                  ^^^^^^^^
I think "in addition" is better here.

> +register handler touching all the still used types by @code{type_mark_used}.

 "to register a handler that will touch all the types still in use
 with a call to @code{type_mark_used}."

OK with those changes.


  reply	other threads:[~2009-05-25 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25  8:03 Jan Kratochvil
2009-05-25 20:56 ` Eli Zaretskii [this message]
2009-05-26 18:15   ` Jan Kratochvil
2009-05-26 19:38     ` Eli Zaretskii
2009-06-09 20:25 ` Tom Tromey

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=83tz38sxzx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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