Hello GengYu Rao,
,
> So there should be problem with -march=native -ftree-vectorize.
Thank, with your help a little bit of investigation I was able to fully
understand the problem. Here are the steps I took to investigate:
1) I knew the "march=native" flag was already disabled by a patch we
Hi Samuel,
I think the problem lies in the Makefile.
Because for different arch, certain assembly instructions may best
exploit the potential of the hardware. As for the vectorize option, different
kinds of CPU support different SIMD instructions like SSE/SSE2/AVX/AVX2/AVX-512.
So there
Hello,
We've always had problems with t50's new upstream forcing some CPU specific
instructions, like hardcoding "march=native" in the Makefile.
Usually the main signal of this type of problem is the non-reproducibility
of the package, the diff being some assembly instructions.
The problem is
