On 2/18/20 5:35 PM, Jim Wilson wrote:
On Sun, Feb 16, 2020 at 9:02 PM Kito Cheng wrote:
It cause the __builtin_strlen not optimized/folded in test_local_cpy_4,
and the reason is blocked by __builtin_memcpy, it's same issue in
strlenopt-80.c, so I there is two way to fix this issue:
Another po
On Sun, Feb 16, 2020 at 9:02 PM Kito Cheng wrote:
> It cause the __builtin_strlen not optimized/folded in test_local_cpy_4,
> and the reason is blocked by __builtin_memcpy, it's same issue in
> strlenopt-80.c, so I there is two way to fix this issue:
Another possible solution is to use
{ dg-re
> Unlike strlenopt-80.c which is a compile-time test that verifies
> that the optimization successfully folds the strlen expressions,
> strlenopt-81.c is a runtime test that verifies the optimization
> isn't done when it might not be safe. It shouldn't fail anywhere,
> whether or not the optimiza
On 2/13/20 8:34 PM, Kito Cheng wrote:
- strlenopt-81.c has same limitation as strlenopt-80.c, this
optimization only work when memcpy expand into load/store.
Unlike strlenopt-80.c which is a compile-time test that verifies
that the optimization successfully folds the strlen expressions,
s
