From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: fix virtual base class bugs
Date: Tue, 02 Feb 2010 16:47:00 -0000 [thread overview]
Message-ID: <m3wryv1t5m.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3k4v07fqp.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri, 29 Jan 2010 14:39:26 -0700")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> This second patch removes TYPE_DECLARED_TYPE and a bunch of related
Tom> constants. These are not currently used in gdb, except by accident:
Tom> when a cplus_struct_type is allocated, the declared_type field is set to
Tom> 0 (== TYPE_DECLARED_CLASS).
Tom> In its place I put a single bit into main_type to indicate whether a
Tom> structure was declared using "struct" or "class". I could have put this
Tom> into cplus_struct_type .. but that seems awfully heavy for a single bit
Tom> of information.
I've committed this as well.
Tom
next prev parent reply other threads:[~2010-02-02 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 16:31 Tom Tromey
2010-01-29 21:39 ` Tom Tromey
2010-02-02 16:47 ` Tom Tromey [this message]
2010-02-02 16:45 ` Tom Tromey
2010-02-03 5:30 ` Jan Kratochvil
2010-02-03 18:24 ` 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=m3wryv1t5m.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
/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