public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Devang Patel <dpatel@apple.com>
To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Cc: "gcc@gcc.gnu.org list" <gcc@gcc.gnu.org>,
	Jason Merrill <jason@redhat.com>,
	Richard Henderson <rth@redhat.com>,
	Dorit Naishlos <DORIT@il.ibm.com>,
	Diego Novillo <dnovillo@redhat.com>
Subject: Re: [lno] [RFC] if-conversion and auto vectorizer
Date: Sat, 13 Mar 2004 22:41:00 -0000	[thread overview]
Message-ID: <63C299A6-753F-11D8-9A45-000393A91CAA@apple.com> (raw)
In-Reply-To: <20040313092438.GA6767@atrey.karlin.mff.cuni.cz>


On Mar 13, 2004, at 1:24 AM, Zdenek Dvorak wrote:

[snip]

>>   # BLOCK 2
>>   # PRED: 1 [79.0%]  (true,exec)
>> <L1>:;
>>   T.1_9 = if (1 && T.0_3 > 0)
>
> why this "1 &&" part?

Its because, I have not simplified conditional boolean expressions yet.

[snip]

>>
>> I spent lot of time unnecessary to create super block inside loop by
>> merging block 2 and 3 into block 1.
>>
>> If vectorizer can not vectorize this loop then it will be reverted to
>> original form using loop versioning. Am I on the right track ?
>
> I am not at all sure what you want to achieve with this transformation;
> it seems to me that you haven't done anything that could possibly make
> vectorizer's work easier.

After transforming statements, I should be able to merge all blocks
in one super block inside loop. Once that is done vectorizer just needs
to do one-to-one replacement.

--
Devang

  reply	other threads:[~2004-03-13 22:41 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
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 [this message]
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=63C299A6-753F-11D8-9A45-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=rakdver@atrey.karlin.mff.cuni.cz \
    --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).