On Tue, Jun 2, 2015 at 11:37 AM, Bin.Cheng amker.ch...@gmail.com wrote:
On Tue, May 26, 2015 at 5:04 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Sun, May 24, 2015 at 8:47 AM, Bin.Cheng amker.ch...@gmail.com wrote:
On Fri, May 22, 2015 at 7:45 PM, Richard Biener
On Tue, May 26, 2015 at 5:04 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Sun, May 24, 2015 at 8:47 AM, Bin.Cheng amker.ch...@gmail.com wrote:
On Fri, May 22, 2015 at 7:45 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Wed, May 20, 2015 at 11:41 AM, Bin Cheng
On Sun, May 24, 2015 at 8:47 AM, Bin.Cheng amker.ch...@gmail.com wrote:
On Fri, May 22, 2015 at 7:45 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Wed, May 20, 2015 at 11:41 AM, Bin Cheng bin.ch...@arm.com wrote:
Hi,
As we know, GCC is too conservative when checking overflow
On Fri, May 22, 2015 at 7:45 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Wed, May 20, 2015 at 11:41 AM, Bin Cheng bin.ch...@arm.com wrote:
Hi,
As we know, GCC is too conservative when checking overflow behavior in SCEV
and loop related optimizers. Result is some variable can't be
On Wed, May 20, 2015 at 11:41 AM, Bin Cheng bin.ch...@arm.com wrote:
Hi,
As we know, GCC is too conservative when checking overflow behavior in SCEV
and loop related optimizers. Result is some variable can't be recognized as
scalar evolution and thus optimizations are missed. To be specific,
Hi,
As we know, GCC is too conservative when checking overflow behavior in SCEV
and loop related optimizers. Result is some variable can't be recognized as
scalar evolution and thus optimizations are missed. To be specific,
optimizers like ivopts and vectorizer are affected.
This issue is more
