From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] rearrange struct value to save memory
Date: Thu, 16 Jan 2014 21:54:00 -0000 [thread overview]
Message-ID: <878uuflhht.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1389294182-982-1-git-send-email-tromey@redhat.com> (Tom Tromey's message of "Thu, 9 Jan 2014 12:03:02 -0700")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> This patch rearranges struct value a tiny bit, moving the "regnum"
Tom> field into a hole. This saves 8 bytes per value on a 64-bit machine,
Tom> and 4 bytes per value on a 32 bit machine. I think it does not
Tom> negatively affect readability or performance.
Tom> Built and regtested on x86-64 Fedora 18.
I'm checking this in now.
Tom
prev parent reply other threads:[~2014-01-16 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 19:03 Tom Tromey
2014-01-10 3:32 ` Yao Qi
2014-01-10 17:12 ` Tom Tromey
2014-01-13 20:02 ` Tom Tromey
2014-01-14 13:50 ` Yao Qi
2014-01-16 21:54 ` Tom Tromey [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=878uuflhht.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).