From: Jakub Jelinek <jakub@redhat.com>
To: Dimitrios Apostolou <jimis@gmx.net>
Cc: gcc-patches@gcc.gnu.org, Steven Bosscher <stevenb.gcc@gmail.com>
Subject: Re: mem_attrs_htab
Date: Mon, 22 Aug 2011 09:43:00 -0000 [thread overview]
Message-ID: <20110822080451.GQ2687@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.02.1108221054070.1374@localhost.localdomain>
On Mon, Aug 22, 2011 at 10:58:48AM +0300, Dimitrios Apostolou wrote:
> the future. I didn't like hashing addresses either, and I was
> surprised I saw no regressions.
Hashing on the expr address as well just results in smaller sharing
in the hash table (i.e. if the expr has different address, but is considered
equal). The hashing of mem attrs is done just to reduce memory overhead.
Jakub
next prev parent reply other threads:[~2011-08-22 8:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 7:50 Various minor speed-ups Dimitrios Apostolou
2011-08-22 7:53 ` graphds.[ch]: alloc_pool for edges Dimitrios Apostolou
2011-08-22 8:46 ` Jakub Jelinek
2011-08-22 10:11 ` Richard Guenther
2011-08-22 7:53 ` mem_attrs_htab Dimitrios Apostolou
2011-08-22 8:37 ` mem_attrs_htab Jakub Jelinek
2011-08-22 9:39 ` mem_attrs_htab Dimitrios Apostolou
2011-08-22 9:43 ` Jakub Jelinek [this message]
2011-08-22 10:45 ` mem_attrs_htab Richard Guenther
2011-08-22 11:11 ` mem_attrs_htab Jakub Jelinek
2011-08-22 11:54 ` mem_attrs_htab Richard Guenther
2011-08-22 16:13 ` mem_attrs_htab Michael Matz
2011-08-22 7:59 ` tree-ssa*: reduce malloc() calls by preallocating hot VECs on the stack Dimitrios Apostolou
2011-08-22 10:07 ` Richard Guenther
2011-08-22 8:05 ` tree-ssa-structalias.c: alloc_pool for struct equiv_class_label Dimitrios Apostolou
2011-08-22 9:01 ` Dimitrios Apostolou
2011-08-22 10:25 ` Richard Guenther
2011-08-22 11:26 ` Dimitrios Apostolou
2011-08-22 8:43 ` Various minor speed-ups Dimitrios Apostolou
2011-08-22 11:01 ` Richard Guenther
2011-08-22 9:44 ` Dimitrios Apostolou
2011-08-22 9:50 ` cse.c: preferable() Dimitrios Apostolou
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=20110822080451.GQ2687@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimis@gmx.net \
--cc=stevenb.gcc@gmail.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).