On Mon, Oct 22, 2012 at 10:31 PM, Marc Glisse wrote:
> On Mon, 15 Oct 2012, Richard Biener wrote:
>
>> On Fri, Oct 12, 2012 at 4:07 PM, Marc Glisse wrote:
>>>
>>> On Sat, 29 Sep 2012, Marc Glisse wrote:
>>>
1) it handles constant folding of vector comparisons,
2) it fixes another p
On Mon, 15 Oct 2012, Richard Biener wrote:
On Fri, Oct 12, 2012 at 4:07 PM, Marc Glisse wrote:
On Sat, 29 Sep 2012, Marc Glisse wrote:
1) it handles constant folding of vector comparisons,
2) it fixes another place where vectors are not expected
Here is a new version of this patch.
In a
On Mon, Oct 15, 2012 at 3:51 PM, Marc Glisse wrote:
> On Mon, 15 Oct 2012, Richard Biener wrote:
>
>>>else if ((code == BIT_NOT_EXPR
>>> && TYPE_PRECISION (TREE_TYPE (cond)) == 1)
>>>|| (code == BIT_XOR_EXPR
>>> - && integer_onep (gimple_ass
On Mon, 15 Oct 2012, Richard Biener wrote:
else if ((code == BIT_NOT_EXPR
&& TYPE_PRECISION (TREE_TYPE (cond)) == 1)
|| (code == BIT_XOR_EXPR
- && integer_onep (gimple_assign_rhs2 (def_stmt
+ && ((gimple_assign_rhs_code
On Fri, Oct 12, 2012 at 4:07 PM, Marc Glisse wrote:
> On Sat, 29 Sep 2012, Marc Glisse wrote:
>
>> 1) it handles constant folding of vector comparisons,
>>
>> 2) it fixes another place where vectors are not expected
>
>
> Here is a new version of this patch.
>
> In a first try, I got bitten by the
On Sat, 29 Sep 2012, Marc Glisse wrote:
1) it handles constant folding of vector comparisons,
2) it fixes another place where vectors are not expected
Here is a new version of this patch.
In a first try, I got bitten by the operator priorities in "a && b?c:d",
which g++ doesn't warn about.
On Sat, Sep 29, 2012 at 3:25 PM, Marc Glisse wrote:
> Hello,
>
> this patch does 2 things (I should have split it in 2, but the questions go
> together):
>
> 1) it handles constant folding of vector comparisons,
>
> 2) it fixes another place where vectors are not expected (I'll probably wait
> to
Hello,
this patch does 2 things (I should have split it in 2, but the questions
go together):
1) it handles constant folding of vector comparisons,
2) it fixes another place where vectors are not expected (I'll probably
wait to have front-end support and testcases to do more of those, but
t