From: Marc Glisse <marc.glisse@inria.fr>
To: "Bin.Cheng" <amker.cheng@gmail.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>,
Richard Biener <richard.guenther@gmail.com>
Subject: Re: [PATCH GCC][1/2]Feed bound computation to folder in loop split
Date: Mon, 24 Jul 2017 13:59:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1707241556250.2780@stedding.saclay.inria.fr> (raw)
In-Reply-To: <CAHFci28LjBpSzhu-LvGVuwbEJoBsNSQEaH17cbL_4vPbWEgpoA@mail.gmail.com>
On Mon, 24 Jul 2017, Bin.Cheng wrote:
> But since definition of _197 isn't in current stmt sequence, call "o31
> = do_valueize (valueize, o31)" will return NULL. As a result, it's
> not matched.
Wait, actually, how was your fold_build* version working? Why was the
first addition "in the current generic tree" and why isn't it "in current
stmt sequence"?
--
Marc Glisse
next prev parent reply other threads:[~2017-07-24 13:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 13:07 Bin Cheng
2017-06-16 10:49 ` Richard Biener
2017-06-16 13:06 ` Bin.Cheng
2017-06-16 13:10 ` Richard Biener
2017-06-16 13:31 ` Bin.Cheng
2017-06-16 16:16 ` Richard Biener
2017-06-16 16:23 ` Bin.Cheng
2017-06-16 16:48 ` Marc Glisse
2017-06-16 16:58 ` Bin.Cheng
2017-06-16 17:04 ` Andrew Pinski
2017-07-24 11:45 ` Bin.Cheng
2017-07-24 12:16 ` Marc Glisse
2017-07-24 13:49 ` Bin.Cheng
2017-07-24 13:59 ` Marc Glisse [this message]
2017-07-24 14:06 ` Bin.Cheng
2017-07-24 14:31 ` Marc Glisse
2017-07-24 14:37 ` Bin.Cheng
2017-07-24 14:52 ` Marc Glisse
2017-07-25 14:32 ` Richard Biener
2017-07-25 17:45 ` Marc Glisse
2017-07-26 7:48 ` Richard Biener
2017-07-26 9:08 ` Richard Sandiford
2017-07-26 9:38 ` Marc Glisse
2017-07-26 9:45 ` Richard Sandiford
2017-07-26 9:57 ` Marc Glisse
2017-07-26 11:13 ` Richard Biener
2017-07-26 11:46 ` Richard Biener
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.DEB.2.20.1707241556250.2780@stedding.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=amker.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@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).