Re: Do we need to do a loop invariant motion after loop interchange ?

2020-02-12 Thread Li Jia He
Hi, On 2019/11/25 5:55 PM, Bin.Cheng wrote: On Mon, Nov 25, 2019 at 5:29 PM Li Jia He wrote: On 2019/11/24 2:26 PM, Bin.Cheng wrote: On Fri, Nov 22, 2019 at 3:23 PM Bin.Cheng wrote: On Fri, Nov 22, 2019 at 3:19 PM Richard Biener wrote: On November 22, 2019 6:51:38 AM GMT+01:00, Li

Re: Do we need to do a loop invariant motion after loop interchange ?

2019-11-25 Thread Li Jia He
On 2019/11/24 2:26 PM, Bin.Cheng wrote: On Fri, Nov 22, 2019 at 3:23 PM Bin.Cheng wrote: On Fri, Nov 22, 2019 at 3:19 PM Richard Biener wrote: On November 22, 2019 6:51:38 AM GMT+01:00, Li Jia He wrote: On 2019/11/21 8:10 PM, Richard Biener wrote: On Thu, Nov 21, 2019 at 10:22 AM

Re: Do we need to do a loop invariant motion after loop interchange ?

2019-11-21 Thread Li Jia He
On 2019/11/21 8:10 PM, Richard Biener wrote: On Thu, Nov 21, 2019 at 10:22 AM Li Jia He wrote: Hi, I found for the follow code: #define N 256 int a[N][N][N], b[N][N][N]; int d[N][N], c[N][N]; void __attribute__((noinline)) double_reduc (int n) { for (int k = 0; k < n

Do we need to do a loop invariant motion after loop interchange ?

2019-11-21 Thread Li Jia He
Hi, I found for the follow code: #define N 256 int a[N][N][N], b[N][N][N]; int d[N][N], c[N][N]; void __attribute__((noinline)) double_reduc (int n) { for (int k = 0; k < n; k++) { for (int l = 0; l < n; l++) { c[k][l] = 0; for (int m = 0; m < n; m++) c[k][

Re: Can we vectorize the code below ?

2019-06-12 Thread Li Jia He
On 2019/6/12 4:04 PM, Richard Biener wrote: On Wed, Jun 12, 2019 at 5:22 AM Li Jia He wrote: Hi, I recently did some analysis on the automatic vectorization of gcc, I found that singed char can not be vectorized in the following code. --- #define ITERATIONS 100 #if defined

Can we vectorize the code below ?

2019-06-11 Thread Li Jia He
Hi, I recently did some analysis on the automatic vectorization of gcc, I found that singed char can not be vectorized in the following code. --- #define ITERATIONS 100 #if defined(do_reduce_signed_char) #define TYPE signed char #elif defined(do_reduce_unsigned_char) #define TYPE unsigned

Re: Possible gcc 4.8.5 bug about RELOC_HIDE marcro in latest kernel code

2017-09-21 Thread Jia He
在 9/21/2017 5:25 PM, Jia He Wrote: Hi Andrew, I tried centos 7.4 gcc 4.8.5-16, which seems to announce to fix this issue. And I checked the source code, the patch had been included in. My fault. All the gcc related rpms are needed to upgrade to 4.8.5-16(only upgrading gcc*.rpm is not

Re: Possible gcc 4.8.5 bug about RELOC_HIDE marcro in latest kernel code

2017-09-21 Thread Jia He
Hi Wilcon The 4.8.5 is default gcc version for centos 7.x Ok, I will consider to upgrade the gcc version. Thanks for your advice. Cheers, Justin 在 9/21/2017 8:56 PM, Wilco Dijkstra Wrote: Hi Justin, I tried centos 7.4 gcc 4.8.5-16, which seems to announce to fix this issue. And I checke

Re: Possible gcc 4.8.5 bug about RELOC_HIDE marcro in latest kernel code

2017-09-21 Thread Jia He
procedure? Thanks a lot! Cheers, Justin On 9/21/2017 2:58 PM, Andrew Pinski Wrote: On Wed, Sep 20, 2017 at 11:51 PM, Jia He wrote: 转发的消息 主题: Possible gcc 4.8.5 bug about RELOC_HIDE marcro 日期: Thu, 21 Sep 2017 14:31:55 +0800 发件人:Jia He 收件人:linux-arm-ker

Re: Possible gcc 4.8.5 bug about RELOC_HIDE marcro in latest kernel code

2017-09-21 Thread Jia He
Thanks a lot, Andrew Seems the centos 7.x still use gcc 4.8.5 Does gcc has any plan to push this fix to rhel? It is really a big bug for arm64 Cheers, Justin 在 2017/9/21 14:58, Andrew Pinski 写道: On Wed, Sep 20, 2017 at 11:51 PM, Jia He wrote: 转发的消息 主题: Possible

Fwd: Possible gcc 4.8.5 bug about RELOC_HIDE marcro in latest kernel code

2017-09-20 Thread Jia He
转发的消息 主题: Possible gcc 4.8.5 bug about RELOC_HIDE marcro 日期: Thu, 21 Sep 2017 14:31:55 +0800 发件人:Jia He 收件人:linux-arm-ker...@lists.infradead.org, linux-ker...@vger.kernel.org I tried to build kernel 4.14-rc1 on a arm64 server in distro centos 7.3. The gcc