Re: [GOOGLE] Builtins handling in IVOPT

2014-01-23 Thread Xinliang David Li
Two patches are ok with the following change * change PARAM_AVG_LOOP_NITER to PARAM_IVOPT_AVG_LOOP_NITER; (The base version of the patch is not correct). thanks, David On Wed, Jan 22, 2014 at 9:52 PM, Wei Mi wrote: > Comments added. I create another patch to add the parameter for AVG_LOOP_ITE

Re: [GOOGLE] Builtins handling in IVOPT

2014-01-22 Thread Wei Mi
Comments added. I create another patch to add the parameter for AVG_LOOP_ITER. Both patches are attached. Thanks, Wei. On Wed, Jan 22, 2014 at 4:42 PM, Xinliang David Li wrote: > On Wed, Jan 22, 2014 at 2:23 PM, Wei Mi wrote: >> This patch handles the mem access builtins in ivopt. The original

Re: [GOOGLE] Builtins handling in IVOPT

2014-01-22 Thread Xinliang David Li
On Wed, Jan 22, 2014 at 2:23 PM, Wei Mi wrote: > This patch handles the mem access builtins in ivopt. The original > problem described here: > http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02648.html > > Bootstrapped and passed regression test. Performance test ok for > plain, fdo and lipo. Ok for

[GOOGLE] Builtins handling in IVOPT

2014-01-22 Thread Wei Mi
This patch handles the mem access builtins in ivopt. The original problem described here: http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02648.html Bootstrapped and passed regression test. Performance test ok for plain, fdo and lipo. Ok for google 4.8 branch? Thanks, Wei. --- /usr/local/google/hom