From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Improve VEC_BASE
Date: Fri, 11 Nov 2011 08:27:00 -0000 [thread overview]
Message-ID: <4EBCB98C.1010904@redhat.com> (raw)
In-Reply-To: <20111107212547.GO27375@tyan-ft48-01.lab.bos.redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/07/11 14:25, Jakub Jelinek wrote:
> Hi!
>
> This patch attempts to optimize VEC_BASE if we know that offsetof
> of base is 0 (unless the compiler is doing something strange, it is
> true). It doesn't have a clear code size effect, some .text
> sections grew, supposedly because of more inlining, some .text
> sections shrunk.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux.
>
> 2011-11-07 Jakub Jelinek <jakub@redhat.com>
>
> * vec.h (VEC_BASE): If base is at offset 0 in the structure, use
> &(P)->base even if P is NULL.
Presumably this becomes redundant with we went with Richi's patch?
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOvLmLAAoJEBRtltQi2kC7BNUIAJMJvrpgtSfIrPDZ/JHXM1on
Td5M5ebXO7lgdf5W5SJU5WiuRqHG2N+J/YJ9mJgUaCdLrbKJQXTdU/jbMaJqbwlR
g1LU7nMHM2Kf87zXdJCdcuB7BfMfmVcpNVopuab1GA6nRye9ru3+SXpXbDSiNmeM
1j8r1IEeL37sWPX2opUHgE9bQfaqDigonlPiqw+JxWQXGBpAvy2xS5CNd93RoN80
SLtHnxWoULpwJ16E9mpgTtR8kG8mFYaWAuWDKMpTX21hK/nTIkjGpFEOHddIjI8n
z/c3zUcjrJujQ773qReSEY0tLdtrckS7/Gy01tIc+yMus7VmVfdt4lpabeoXwX4=
=mJd5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-11-11 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 21:34 Jakub Jelinek
2011-11-07 23:25 ` Richard Guenther
2011-11-08 0:34 ` Jeff Law
2011-11-08 10:12 ` Richard Guenther
2011-11-08 10:29 ` Richard Guenther
2011-11-08 19:35 ` Jeff Law
2011-11-08 19:54 ` Jeff Law
2011-11-09 9:42 ` Richard Guenther
2011-11-11 8:27 ` Jeff Law [this message]
2011-11-11 9:42 ` Jakub Jelinek
2011-11-11 20:21 ` Jeff Law
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=4EBCB98C.1010904@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).