Re: [PATCH GCC8][25/33]New loop constraint flags

2017-05-04 Thread Bin.Cheng
On Wed, Apr 26, 2017 at 3:01 PM, Bin.Cheng wrote: > On Wed, Apr 26, 2017 at 2:27 PM, Richard Biener > wrote: >> On Tue, Apr 18, 2017 at 12:51 PM, Bin Cheng wrote: >>> Hi, >>> This patch adds new loop constraint flags marking prologue, epilogue and >>> versioned loops generated >>> by vectorizer

Re: [PATCH GCC8][25/33]New loop constraint flags

2017-04-26 Thread Bin.Cheng
On Wed, Apr 26, 2017 at 2:27 PM, Richard Biener wrote: > On Tue, Apr 18, 2017 at 12:51 PM, Bin Cheng wrote: >> Hi, >> This patch adds new loop constraint flags marking prologue, epilogue and >> versioned loops generated >> by vectorizer, unroller and versioning. These flags will be used in IVOP

Re: [PATCH GCC8][25/33]New loop constraint flags

2017-04-26 Thread Richard Biener
On Tue, Apr 18, 2017 at 12:51 PM, Bin Cheng wrote: > Hi, > This patch adds new loop constraint flags marking prologue, epilogue and > versioned loops generated > by vectorizer, unroller and versioning. These flags will be used in IVOPTs > in order to differentiate > possible hot innermost loop

[PATCH GCC8][25/33]New loop constraint flags

2017-04-18 Thread Bin Cheng
Hi, This patch adds new loop constraint flags marking prologue, epilogue and versioned loops generated by vectorizer, unroller and versioning. These flags will be used in IVOPTs in order to differentiate possible hot innermost loop from others. I also plan to use them to avoid unnecessary cunr