public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/5] Remove struct main_type.vptr_{fieldno,basetype}
Date: Mon, 02 Feb 2015 03:52:00 -0000	[thread overview]
Message-ID: <20150202035240.GI4525@adacore.com> (raw)
In-Reply-To: <m361buac8x.fsf@sspiff.org>

> Anytime you can reduce the size of struct main_type that's A Good Thing.
> Alas in this case my motivation, besides more general cleanup (will it
> never end?), is that I may wish to add something to struct main_type.
> Now I can, if I need to.
> 
> There are two fields in struct main_type that really shouldn't be there:
> vptr_fieldno, and vptr_basetype.  Every type has to pay the price
> in memory usage for their presence.  The proper place for them is
> in the type_specific field (in this case cplus_stuff) which exists
> for this purpose.

Thanks for doing that, Doug.

-- 
Joel

      parent reply	other threads:[~2015-02-02  3:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 19:56 Doug Evans
2015-02-01  5:48 ` Doug Evans
2015-02-02  3:52 ` Joel Brobecker [this message]

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=20150202035240.GI4525@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).