[PATCH] Optimize COND_EXPR where then/else operands are INTEGER_CSTs of different size than the comparison operands
Thu Oct 6 17:50:00 GMT 2011
On 6 October 2011 19:28, Jakub Jelinek <firstname.lastname@example.org> wrote:
> On Thu, Oct 06, 2011 at 07:27:28PM +0200, Ira Rosen wrote:
>> > + i = 1;
>> > + if ((rhs_code == COND_EXPR || rhs_code == VEC_COND_EXPR)
>> I don't understand why we need VEC_COND_EXPR here.
> Only for completeness, as VEC_COND_EXPR is the same weirdo thingie like
> COND_EXPR. I can leave that out if you want.
But we mark stmts that we want to vectorize here. I think that
expecting a vector stmt is confusing. So yes, please, leave it out.
More information about the Gcc-patches