Re: [gimplefe] Parsing __GIMPLE function body

2016-06-01 Thread Prathamesh Kulkarni
On 30 May 2016 at 20:45, Prasad Ghangal wrote: > Hi, > > As David suggested in his rtlfe patch, > this patch recognizes __GIMPLE keyword and switches to > c_parser_parse_gimple_body by providing -fgimple option. > > > diff --git a/gcc/c-family/c-common.c b/gcc/c-family/c-common.c > index 4568cf6..

Re: [gimplefe] Parsing __GIMPLE function body

2016-06-01 Thread Richard Biener
On Wed, Jun 1, 2016 at 9:19 AM, Prathamesh Kulkarni wrote: > On 30 May 2016 at 20:45, Prasad Ghangal wrote: >> Hi, >> >> As David suggested in his rtlfe patch, >> this patch recognizes __GIMPLE keyword and switches to >> c_parser_parse_gimple_body by providing -fgimple option. >> >> >> diff --git

Re: [gimplefe] Parsing __GIMPLE function body

2016-06-01 Thread Prasad Ghangal
On 1 June 2016 at 15:19, Richard Biener wrote: > On Wed, Jun 1, 2016 at 9:19 AM, Prathamesh Kulkarni > wrote: >> On 30 May 2016 at 20:45, Prasad Ghangal wrote: >>> Hi, >>> >>> As David suggested in his rtlfe patch, >>> this patch recognizes __GIMPLE keyword and switches to >>> c_parser_parse_gim

Re: [gimplefe] Parsing __GIMPLE function body

2016-06-01 Thread David Malcolm
On Wed, 2016-06-01 at 12:49 +0530, Prathamesh Kulkarni wrote: > On 30 May 2016 at 20:45, Prasad Ghangal > wrote: > > Hi, > > > > As David suggested in his rtlfe patch, > > this patch recognizes __GIMPLE keyword and switches to > > c_parser_parse_gimple_body by providing -fgimple option. > > [sni

gcc-4.9-20160601 is now available

2016-06-01 Thread gccadmin
Snapshot gcc-4.9-20160601 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20160601/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.9 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

fstrict-enums and value ranges in VRP

2016-06-01 Thread kugan
Hi All, When I compile the following code with g++ using -fstrict-enums and -O2 enum v { OK = 0, NOK = 1, }; int foo0 (enum v a) { if (a > NOK) return 0; return 1; } vrp1 dump looks like: Value ranges after VRP: a.0_1: VARYING _2: [0, 1] a_3(D): VARYING int foo0(v) (v a) { int

Re: fstrict-enums and value ranges in VRP

2016-06-01 Thread Trevor Saunders
On Thu, Jun 02, 2016 at 08:54:36AM +1000, kugan wrote: > Hi All, > > When I compile the following code with g++ using -fstrict-enums and -O2 > > enum v > { > OK = 0, > NOK = 1, > }; > > int foo0 (enum v a) > { > if (a > NOK) > return 0; > return 1; > } > > vrp1 dump looks like: > Va