Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: tromey@redhat.com
Cc: jan.kratochvil@redhat.com (Jan Kratochvil), gdb-patches@sourceware.org
Subject: Re: [patch] [3/5] Types reference counting      [make_function_type-objfile]
Date: Fri, 26 Jun 2009 17:36:00 -0000	[thread overview]
Message-ID: <200906261736.n5QHa0s3008047@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <m3prcqdi2z.fsf@fleche.redhat.com> from "Tom Tromey" at Jun 26, 2009 11:24:04 AM

Tom Tromey wrote:
> >>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:
> 
> Ulrich> Mostly.  We still can have the case were TYPE_OBJFILE(A) is NULL but
> Ulrich> TYPE_OBJFILE(B) is non-NULL, for example where A is a temporary array
> Ulrich> and B the element type.
> 
> Ulrich> The way I see the invariant is
> Ulrich>   If Type A references Type B *and* A is objfile-associated
> Ulrich>   *then* B must be associated to the same objfile
> 
> Suppose we have A as an array type with a NULL objfile, and with
> element type B, which has an objfile.
> 
> If we have a convenience variable of type A, and the objfile is
> deleted, I don't think preserve_values will copy type B.  That is
> because we only check the value's immediate objfile to decide whether
> we need to do a type copy.

Hmm, good point.

> Therefore it seems to me that the invariant must be TYPE_OBJFILE(A) ==
> TYPE_OBJFILE(B), for all related types A and B.

I'm not sure how to best implement this invariant -- we *need* to support
the case of a temporary array of pre-existing element types (e.g. for
value_slice etc.) ...

We don't want to allocate the temporary array types per-objfile, because
then they will not be subject to garbage collection (and if the user does
something that causes a lot of those arrays to be generated before the
objfile is unloaded, this could cause a significant leak).

I guess we could force the element type to be copied at the time the
array type is allocated.  In the alternative, we could change 
preserve_values to do the recursive check even if the main type is
not objfile-associated.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2009-06-26 17:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 10:22 Jan Kratochvil
2009-04-16 21:43 ` Tom Tromey
2009-05-01 14:44   ` Jan Kratochvil
2009-06-26 13:23     ` Ulrich Weigand
2009-06-26 13:26       ` [rfc] Always use per-objfile types in symbol readers Ulrich Weigand
2009-06-26 13:29       ` [rfc] Fix Java type allocation and revert make_function_type change Ulrich Weigand
2009-06-26 16:12       ` [patch] [3/5] Types reference counting [make_function_type-objfile] Tom Tromey
2009-06-26 17:06         ` Ulrich Weigand
2009-06-26 16:40       ` Jan Kratochvil
2009-06-26 17:12         ` Ulrich Weigand
2009-06-26 17:24           ` Tom Tromey
2009-06-26 17:36             ` Ulrich Weigand [this message]
2009-06-26 18:04               ` Tom Tromey
2009-06-29 13:25         ` Ulrich Weigand

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=200906261736.n5QHa0s3008047@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=tromey@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