From: Devang Patel <dpatel@apple.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: "gcc@gcc.gnu.org list" <gcc@gcc.gnu.org>,
Dorit Naishlos <DORIT@il.ibm.com>,
Richard Henderson <rth@redhat.com>,
Jason Merrill <jason@redhat.com>
Subject: Re: [lno] [RFC] if-conversion and auto vectorizer
Date: Fri, 05 Mar 2004 19:28:00 -0000 [thread overview]
Message-ID: <1B61F022-6EDB-11D8-AEC8-000393A91CAA@apple.com> (raw)
In-Reply-To: <1078514261.20630.11.camel@localhost.localdomain>
On Mar 5, 2004, at 11:17 AM, Diego Novillo wrote:
> On Fri, 2004-03-05 at 14:05, Devang Patel wrote:
>
>> a = select a1, a2, c
>> b = select b1, b2, c1
>> c = select a1, b1, c2
>>
>> We want to put all three statements in one basic block.
>>
> Why would it? They still look like a MODIFY_EXPR.
>
> MODIFY_EXPR <a, COND_EXPR <a1, a2, c>>
> MODIFY_EXPR <b, COND_EXPR <b1, b2, c1>>
> MODIFY_EXPR <c, COND_EXPR <a1, b1, c2>>
My worry is it would it cause confusion to gimple verifiers?
Would it be possible that during verification this is flagged
as non gimple expression ? If not and CFG routines want alter
control flow when they see it then its fine. I do not know
if someone else will be tickled by COND_EXPR or not.
But so far it seems that's not the case.
Thanks,
--
Devang
next prev parent reply other threads:[~2004-03-05 19:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 19:59 Devang Patel
2004-03-04 20:12 ` Andrew Pinski
2004-03-04 20:39 ` Devang Patel
2004-03-04 21:03 ` Richard Henderson
2004-03-05 19:06 ` Devang Patel
2004-03-05 19:17 ` Diego Novillo
2004-03-05 19:22 ` Diego Novillo
2004-03-05 19:28 ` Devang Patel [this message]
2004-03-05 19:41 ` Diego Novillo
2004-03-05 19:44 ` Diego Novillo
2004-03-12 18:45 ` Devang Patel
2004-03-13 9:24 ` Zdenek Dvorak
2004-03-13 22:41 ` Devang Patel
2004-03-14 10:59 ` Dorit Naishlos
2004-03-14 10:57 Fw: " Dorit Naishlos
2004-03-14 19:22 ` Andrew Pinski
2004-03-14 22:31 ` Daniel Berlin
2004-03-15 2:29 ` Alex Rosenberg
2004-03-15 22:38 ` Richard Henderson
2004-03-15 23:08 ` Devang Patel
2004-03-15 23:20 ` Richard Henderson
2004-03-16 0:02 ` Devang Patel
2004-03-16 0:07 ` Diego Novillo
2004-03-16 0:45 ` Richard Henderson
2004-03-16 3:02 ` Diego Novillo
2004-03-16 3:33 ` Richard Henderson
2004-03-16 6:33 ` Devang Patel
2004-03-15 22:42 Robert Dewar
2004-03-15 23:08 ` Richard Henderson
2004-03-16 3:46 Chris Lattner
2004-03-16 5:33 Robert Dewar
2004-03-16 6:54 ` Richard Henderson
2004-03-16 12:27 Robert Dewar
2004-03-16 18:32 ` Richard Henderson
2004-03-16 22:51 ` Toon Moene
2004-03-16 23:10 ` Joseph S. Myers
2004-03-16 23:28 ` Toon Moene
2004-03-16 23:37 ` Richard Henderson
2004-03-16 23:42 ` Toon Moene
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=1B61F022-6EDB-11D8-AEC8-000393A91CAA@apple.com \
--to=dpatel@apple.com \
--cc=DORIT@il.ibm.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=rth@redhat.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).