From: Paolo Bonzini <bonzini@gnu.org>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] gcse.c: don't compute a mapping from CUID to INSN
Date: Sun, 11 Nov 2007 10:22:00 -0000 [thread overview]
Message-ID: <4736C152.7010407@gnu.org> (raw)
In-Reply-To: <571f6b510711091446oe4ee8a1sa7e28fa1ca9da675@mail.gmail.com>
Steven Bosscher wrote:
> And with patch this time.
>
> On Nov 9, 2007 11:46 PM, Steven Bosscher <stevenb.gcc@gmail.com> wrote:
>> Hi,
>>
>> I've long lost the illusion that anyone here cares one serious bit
>> about compile time. But having loops over all insns just for the sake
>> of it is surely too much even for the most stubborn pass-adding,
>> compile time increasing gcc hacker around here?
It's actually possible to replace CUIDs with LUIDs altogether (the
difference is only that LUIDs are per-basic-block, but this should not
matter in any sane^Wmodern pass, and in fact for GCSE it does not). I
have a patch, but it's not suitable for stage3 (unless we use the excuse
that df slowed down the compiler, and the patch exploits one benefit of df).
Paolo
next prev parent reply other threads:[~2007-11-11 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 23:59 Steven Bosscher
2007-11-10 1:09 ` Steven Bosscher
2007-11-11 10:22 ` Paolo Bonzini [this message]
2007-11-11 11:49 ` Steven Bosscher
2007-11-10 8:27 ` Richard Guenther
2007-11-10 16:32 ` Jakub Jelinek
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=4736C152.7010407@gnu.org \
--to=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--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).