From: Michael Elizabeth Chastain <mec@shout.net>
To: ezannoni@redhat.com, gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: [rfa] space reduction in gdbtypes.h
Date: Wed, 20 Aug 2003 17:46:00 -0000 [thread overview]
Message-ID: <200308201746.h7KHkdkV009277@duracef.shout.net> (raw)
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?
Michael C
2003-08-20 Michael Chastain <mec@shout.net>
* gdbtypes.h (struct main_type): Rearrange to save space.
Index: gdbtypes.h
===================================================================
RCS file: /cvs/src/src/gdb/gdbtypes.h,v
retrieving revision 1.48
diff -u -r1.48 gdbtypes.h
--- gdbtypes.h 23 Jun 2003 21:05:40 -0000 1.48
+++ gdbtypes.h 20 Aug 2003 02:53:46 -0000
@@ -274,10 +274,6 @@
struct main_type
{
- /* Code for kind of type */
-
- enum type_code code;
-
/* Name of this type, or NULL if none.
This is used for printing only, except by poorly designed C++ code.
@@ -298,6 +294,10 @@
char *tag_name;
+ /* Code for kind of type */
+
+ ENUM_BITFIELD(type_code) code : 8;
+
/* FIXME, these should probably be restricted to a Fortran-specific
field in some fashion. */
#define BOUND_CANNOT_BE_DETERMINED 5
@@ -306,8 +306,8 @@
#define BOUND_BY_REF_IN_REG 2
#define BOUND_BY_VALUE_IN_REG 1
#define BOUND_SIMPLE 0
- int upper_bound_type;
- int lower_bound_type;
+ int upper_bound_type : 4;
+ int lower_bound_type : 4;
/* Every type is now associated with a particular objfile, and the
type is allocated on the type_obstack for that objfile. One problem
@@ -340,6 +340,15 @@
short nfields;
+ /* Field number of the virtual function table pointer in
+ VPTR_BASETYPE. If -1, we were unable to find the virtual
+ function table pointer in initial symbol reading, and
+ fill_in_vptr_fieldno should be called to find it if possible.
+
+ Unused if this type does not have virtual functions. */
+
+ short vptr_fieldno;
+
/* For structure and union types, a description of each field.
For set and pascal array types, there is one "field",
whose type is the domain type of the set or array.
@@ -420,15 +429,6 @@
Unused otherwise. */
struct type *vptr_basetype;
-
- /* Field number of the virtual function table pointer in
- VPTR_BASETYPE. If -1, we were unable to find the virtual
- function table pointer in initial symbol reading, and
- fill_in_vptr_fieldno should be called to find it if possible.
-
- Unused if this type does not have virtual functions. */
-
- int vptr_fieldno;
/* Slot to point to additional language-specific fields of this type. */
next reply other threads:[~2003-08-20 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 17:46 Michael Elizabeth Chastain [this message]
2003-08-20 19:55 ` Jim Blandy
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=200308201746.h7KHkdkV009277@duracef.shout.net \
--to=mec@shout.net \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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