From: Jeff Garzik <jeff@garzik.org>
To: Kamil Dudka <kdudka@redhat.com>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>,
Pekka J Enberg <penberg@cs.helsinki.fi>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: linearize bug?
Date: Sat, 27 Aug 2011 18:07:33 -0400 [thread overview]
Message-ID: <4E596AA5.9080401@garzik.org> (raw)
In-Reply-To: <201108271334.17659.kdudka@redhat.com>
------------------------------------------
--- a/cse.c
+++ b/cse.c
@@ -316,12 +316,14 @@ static struct instruction * try_to_cse(struct
entrypoint *
b1 = i1->bb;
b2 = i2->bb;
+#if 0
/*
* PHI-nodes do not care where they are - the only thing that
matters
* are the PHI _sources_.
*/
if (i1->opcode == OP_PHI)
return cse_one_instruction(i1, i2);
+#endif
--------------------------------------
That patch definitely gets much farther along in terms of handling loops.
Jeff
next prev parent reply other threads:[~2011-08-27 22:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 6:29 linearize bug? Jeff Garzik
2011-08-27 11:34 ` Kamil Dudka
2011-08-27 15:29 ` Linus Torvalds
2011-08-27 15:37 ` Jeff Garzik
2011-08-27 15:53 ` Linus Torvalds
2011-08-27 16:54 ` Kamil Dudka
2011-08-27 17:13 ` Linus Torvalds
2011-08-27 17:27 ` Linus Torvalds
2011-08-27 19:26 ` Linus Torvalds
2011-08-27 20:03 ` Jeff Garzik
2011-08-28 6:26 ` Pekka Enberg
2011-08-27 23:39 ` [PATCH] cse: update PHI users when throwing away an instruction Kamil Dudka
2011-08-28 0:34 ` Linus Torvalds
2011-08-28 6:32 ` Christopher Li
2011-08-28 6:33 ` Pekka Enberg
2011-08-28 8:53 ` Jeff Garzik
2011-08-27 22:07 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-12 4:09 linearize bug? Jeff Garzik
2006-11-13 4:43 ` Linus Torvalds
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=4E596AA5.9080401@garzik.org \
--to=jeff@garzik.org \
--cc=kdudka@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@linux-foundation.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 NNTP newsgroup(s).