From: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
To: Dorit Nuzman <DORIT@il.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch] vectorizer cleanups (and prep for outer-loop vectorization) - part 3/5
Date: Thu, 12 Apr 2007 12:11:00 -0000 [thread overview]
Message-ID: <20070412121122.GA8089@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <OF43BC40F0.0DC80E04-ONC22572B9.0071795B-C22572BA.00414A33@il.ibm.com>
Hello,
> > > o A bunch of other cleanups (that are not necessarily inspired by
> > > outer-loop vectorization): Factor out code from
> > > vect_mark_stmts_to_be_vectorized to process_use;
>
> Tested on the vectorizer testcases
> Bootstrapped and passed full testing on powerpc-linux together with the
> other parts of this patch.
>
> thanks,
> dorit
>
> ChangeLog:
>
> * tree-vect-analyze.c (process_use): New function.
> (vect_mark_stmts_to_be_vectorized): Factor out code to process_use.
> Check phis in all bbs.
> * tree-vectorizer.c (vect_is_simple_use): Remove redundant checks.
> *************** vect_is_simple_use (tree operand, loop_v
> *** 1730,1742 ****
> {
> case PHI_NODE:
> *def = PHI_RESULT (*def_stmt);
> - gcc_assert (*dt == vect_induction_def || *dt == vect_reduction_def
> - || *dt == vect_invariant_def);
> break;
>
> case GIMPLE_MODIFY_STMT:
> *def = GIMPLE_STMT_OPERAND (*def_stmt, 0);
> - gcc_assert (*dt == vect_loop_def || *dt == vect_invariant_def);
> break;
>
> default:
> --- 1721,1730 ----
I would prefer to keep these asserts, unless there is some trivial
reason that makes them redundant (that I do not see). Otherwise OK.
Zdenek
next prev parent reply other threads:[~2007-04-12 12:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 8:43 [patch] vectorizer cleanups (and prep for outer-loop vectorization) Dorit Nuzman
2007-04-02 9:48 ` Zdenek Dvorak
2007-04-02 9:55 ` Zdenek Dvorak
2007-04-11 11:51 ` [patch] vectorizer cleanups (and prep for outer-loop vectorization) - part 2/5 Dorit Nuzman
2007-04-11 23:53 ` Zdenek Dvorak
2007-04-14 18:29 ` Dorit Nuzman
2007-04-14 18:56 ` Zdenek Dvorak
2007-04-11 11:51 ` [patch] vectorizer cleanups (and prep for outer-loop vectorization) - part 3/5 Dorit Nuzman
2007-04-12 12:11 ` Zdenek Dvorak [this message]
2007-04-14 18:54 ` Dorit Nuzman
2007-04-14 19:32 ` Zdenek Dvorak
2007-04-11 11:51 ` [patch] vectorizer cleanups (and prep for outer-loop vectorization) - part 4/5 Dorit Nuzman
2007-04-12 12:17 ` Zdenek Dvorak
2007-04-11 11:51 ` [patch] vectorizer cleanups (and prep for outer-loop vectorization) Dorit Nuzman
2007-04-11 11:51 ` [patch] vectorizer cleanups (and prep for outer-loop vectorization) - part 1/5 Dorit Nuzman
2007-04-11 11:51 ` [patch] vectorizer cleanups (and prep for outer-loop vectorization) - part 5/5 Dorit Nuzman
2007-04-12 12:22 ` Zdenek Dvorak
2007-04-12 14:23 ` Daniel Berlin
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=20070412121122.GA8089@atrey.karlin.mff.cuni.cz \
--to=rakdver@atrey.karlin.mff.cuni.cz \
--cc=DORIT@il.ibm.com \
--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).