From: Tom Tromey <tromey@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.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:24:00 -0000 [thread overview]
Message-ID: <m3prcqdi2z.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200906261712.n5QHCXOh026222@d12av02.megacenter.de.ibm.com> (Ulrich Weigand's message of "Fri\, 26 Jun 2009 19\:12\:33 +0200 \(CEST\)")
>>>>> "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.
Therefore it seems to me that the invariant must be TYPE_OBJFILE(A) ==
TYPE_OBJFILE(B), for all related types A and B.
Tom
next prev parent reply other threads:[~2009-06-26 17:24 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 [this message]
2009-06-26 17:36 ` Ulrich Weigand
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=m3prcqdi2z.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=uweigand@de.ibm.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