Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa] space reduction in gdbtypes.h
Date: Wed, 20 Aug 2003 19:55:00 -0000	[thread overview]
Message-ID: <vt2n0e4t855.fsf@zenia.home> (raw)
In-Reply-To: <200308201746.h7KHkdkV009277@duracef.shout.net>


Michael Elizabeth Chastain <mec@shout.net> writes:

> More space reduction!  This is the last of the low-hanging fruit.
> 
>   before: 90001408
>   after:  87068672
> 
> This is a re-arrangement of 'struct main_type'.
> 
>   struct main_type  52  40
> 
> Testing: native i686-pc-linux-gnu, gcc v2 and v3, dwarf-2 and stabs+.
> Full test suite, not regressions.
> 
> Okay to commit?

Yes, with some minor changes:

- I think it's important that this struct start with something that
  indicates which sort of type it represents.  It's weird to have the
  discriminant buried in the middle.  So leave 'code' the first member
  of the structure, and move the {upper,lower}_bound_type fields up.

- Add a short comment indicating that the {upper,lower}_bound_type
  fields pack better at that location.

It's a shame that one needs to make things less clear (e.g., moving
vptr_fieldno away from vptr_basetype) in order to save space.  I wish
there were some way to tell the compiler, "I don't care about the
in-memory ordering of these fields, just pack them as tightly as you
can."


  reply	other threads:[~2003-08-20 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20 17:46 Michael Elizabeth Chastain
2003-08-20 19:55 ` Jim Blandy [this message]
2003-08-21  4:04 ` Andrew Cagney
2003-08-20 20:23 Michael Elizabeth Chastain
2003-08-20 23:02 Michael Elizabeth Chastain
2003-08-21  4:33 Michael Elizabeth Chastain
2003-08-21 14:10 ` Andrew Cagney

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=vt2n0e4t855.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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