Re: [genmatch] reject empty c_expr

2015-07-21 Thread Richard Biener
On Thu, 16 Jul 2015, Richard Biener wrote: > On Thu, 16 Jul 2015, Prathamesh Kulkarni wrote: > > > On 16 July 2015 at 12:39, Richard Biener wrote: > > > On Wed, 15 Jul 2015, Prathamesh Kulkarni wrote: > > > > > >> Hi, > > >> We allow c_expr to be empty which accepts cases like the following: > >

Re: [genmatch] reject empty c_expr

2015-07-16 Thread Richard Biener
On Thu, 16 Jul 2015, Prathamesh Kulkarni wrote: > On 16 July 2015 at 12:39, Richard Biener wrote: > > On Wed, 15 Jul 2015, Prathamesh Kulkarni wrote: > > > >> Hi, > >> We allow c_expr to be empty which accepts cases like the following: > >> > >> (simplify > >> match-operand > >> (if () > >>

Re: [genmatch] reject empty c_expr

2015-07-16 Thread Prathamesh Kulkarni
On 16 July 2015 at 12:39, Richard Biener wrote: > On Wed, 15 Jul 2015, Prathamesh Kulkarni wrote: > >> Hi, >> We allow c_expr to be empty which accepts cases like the following: >> >> (simplify >> match-operand >> (if () >> result-operand)) >> >> (simplify >> match-operand >> {}) > > Y

Re: [genmatch] reject empty c_expr

2015-07-16 Thread Richard Biener
On Wed, 15 Jul 2015, Prathamesh Kulkarni wrote: > Hi, > We allow c_expr to be empty which accepts cases like the following: > > (simplify > match-operand > (if () > result-operand)) > > (simplify > match-operand > {}) Yes we do. We also do not reject various other "bad" forms like

[genmatch] reject empty c_expr

2015-07-15 Thread Prathamesh Kulkarni
Hi, We allow c_expr to be empty which accepts cases like the following: (simplify match-operand (if () result-operand)) (simplify match-operand {}) The attached patch rejects empty c_expr. Ok for trunk after bootstrap + test ? Thank you, Prathamesh 2015-07-15 Prathamesh Kulkarni