From: Richard Guenther <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH][RFC] Force predicate computations to separate stmts
Date: Fri, 13 Aug 2010 15:20:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1008131706490.25856@zhemvz.fhfr.qr> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1050 bytes --]
This forces predicate computation in GIMPLE_CONDs and COND_EXPRs
into separate statements making GIMPLE_ASSIGNs the only place
where predicate computation happens.
This helps streamlining the code and allows for example value-numbering
to do sth with these predicates (and eventually drive jump-threading
from it).
The patch is largely mechanical (and after some mechanics some
helpers were invented but not retrofitted to earlier uses) - it is
a draft. A load of testcase fails are expected because dumps
are different (as usual) and I simply disabled the most ugly
GIMPLE_COND code which is from auto-parallelization.
Other than that the patch bootstraps on x86_64-unknown-linux-gnu
for all languages without -Werror (I managed to partly disable
the new fancy uninitialized variable thing and so we get extra
warnings).
But - I'm fishing for comments (as usual) on this GIMPLE IL change.
(prominent examples where code simplifications were possible are
tree forwprop, VRP and DOM).
Richard.
(no changelog yet, bzipped attachment - it's big)
[-- Attachment #2: Type: APPLICATION/x-bzip, Size: 28193 bytes --]
next reply other threads:[~2010-08-13 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 15:20 Richard Guenther [this message]
2010-08-13 15:22 ` Diego Novillo
2010-08-13 15:32 ` Richard Guenther
2010-08-13 15:48 ` Michael Matz
2010-08-13 16:00 ` Diego Novillo
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=alpine.LNX.2.00.1008131706490.25856@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--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).