rearrange struct value to save memory
This patch rearranges struct value a tiny bit, moving the "regnum" field into a hole. This saves 8 bytes per value on a 64-bit machine, and 4 bytes per value on a 32 bit machine. I think it does not negatively affect readability or performance. Built and regtested on x86-64 Fedora 18. 2014-01-16 Tom Tromey <tromey@redhat.com> * value.c (struct value) <regnum>: Move earlier.
This commit is contained in:
parent
77a1944595
commit
98b1cfdcc8
@ -1,3 +1,7 @@
|
||||
2014-01-16 Tom Tromey <tromey@redhat.com>
|
||||
|
||||
* value.c (struct value) <regnum>: Move earlier.
|
||||
|
||||
2014-01-16 Tom Tromey <tromey@redhat.com>
|
||||
|
||||
* remote.c (extended_remote_create_inferior): Rename from
|
||||
|
@ -216,6 +216,9 @@ struct value
|
||||
/* If the value has been released. */
|
||||
unsigned int released : 1;
|
||||
|
||||
/* Register number if the value is from a register. */
|
||||
short regnum;
|
||||
|
||||
/* Location of value (if lval). */
|
||||
union
|
||||
{
|
||||
@ -324,9 +327,6 @@ struct value
|
||||
taken off this list. */
|
||||
struct value *next;
|
||||
|
||||
/* Register number if the value is from a register. */
|
||||
short regnum;
|
||||
|
||||
/* Actual contents of the value. Target byte-order. NULL or not
|
||||
valid if lazy is nonzero. */
|
||||
gdb_byte *contents;
|
||||
|
Loading…
Reference in New Issue
Block a user