https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81467
--- Comment #3 from alekshs at hotmail dot com --- Aha, ok thanks for the clarification. It was pretty helpful. Regarding clobbering, I was compiling on a Skylake Xeon which has avx512f avx512dq avx512cd avx512bw avx512vl using -march=native... so I didn't expect avx512 detection to be an issue (the registers were present on the cpu and the native flag says go on and use the maximum possible). Perhaps it would be somewhat simpler if it was able to allow clobbering xmm/ymm/zmm16-31 and k-regs based on the native flag (without the conditional ifs). Maybe an improvement (?) for the future (?). Thanks again.
