From: "Steven Bosscher" <stevenb.gcc@gmail.com>
To: "Paolo Bonzini" <bonzini@gnu.org>
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 11:49:00 -0000 [thread overview]
Message-ID: <571f6b510711110126q3c687e2s587180fa4ffeb6c7@mail.gmail.com> (raw)
In-Reply-To: <4736C152.7010407@gnu.org>
On Nov 11, 2007 9:46 AM, Paolo Bonzini <bonzini@gnu.org> wrote:
> 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).
I have a patch just like that -- while working on it I found
CUID_INSN. It seems to me that this would be a suitable change for
stage3, but you have to be careful because you will need new
df_analyze calls to update the LUIDs between the different passes.
Gr.
Steveb
next prev parent reply other threads:[~2007-11-11 9:26 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
2007-11-11 11:49 ` Steven Bosscher [this message]
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=571f6b510711110126q3c687e2s587180fa4ffeb6c7@mail.gmail.com \
--to=stevenb.gcc@gmail.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.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).