On Tue, Oct 28, 2014 at 1:26 PM, Prathamesh Kulkarni
wrote:
> On Tue, Oct 28, 2014 at 3:50 PM, Richard Biener
> wrote:
>> On Mon, Oct 27, 2014 at 3:32 PM, Prathamesh Kulkarni
>> wrote:
>>> I suppose we should reject conditional convert and commutative ops in
>>> result operand ? since it would c
On Tue, Oct 28, 2014 at 3:50 PM, Richard Biener
wrote:
> On Mon, Oct 27, 2014 at 3:32 PM, Prathamesh Kulkarni
> wrote:
>> I suppose we should reject conditional convert and commutative ops in
>> result operand ? since it would create 1-n mapping from match ->
>> result.
>
> Yeah. Same is true fo
On Mon, Oct 27, 2014 at 3:32 PM, Prathamesh Kulkarni
wrote:
> I suppose we should reject conditional convert and commutative ops in
> result operand ? since it would create 1-n mapping from match ->
> result.
Yeah. Same is true for parsing of :type syntax for the match part.
Now that we have a c
I suppose we should reject conditional convert and commutative ops in
result operand ? since it would create 1-n mapping from match ->
result.
* genmatch.c
(fatal_at): New overloaded function with source_location as first parameter.
(has_opt_convert_or_commutative_ops): New function.
(lower)
