Ali Muhammed

There should be **no worrying** about adding flags `-mavx -mavx2` if you use machine not older than 2015 Q3 for AMD and Intel. Because adding `-march=native` may not succeed to...

@error256 Ok! One of my machine is `skylake` and gcc is `11.1.0`. Sure you do know skylake has support for AVX! So when i compile with the flag `-march=native` i...

@error256 > Using -march=native enables all instruction subsets supported by the local machine... This is not truth! Here is the option for `-march=native` on `x86-64 skylake`: ``` gcc -Q -march=native...

The OS should have support for AVX enabled. And that is the same reason why `gdb` does not show `ymm` registers while debugging though you may successfully run AVX code...

It's not a bug! The same thing with clang: 'native' throws an error and `avx2` does not! and gdb version is 10.2 but it does not recognize ymm registers to...

Exactly! So the first option is to check the OS support and add `-march=native` if enabled. And the second option if the OS support is disabled is to check the...

Here was [the hack](https://stackoverflow.com/questions/43750603/gdb-reverse-debugging-avx2) for old ubuntu and i try to find the similar hack for my os.

@Urfoex i just shared the link for those who may have similar problems... But the Codewars solution is much more easier as i've described in two scenarios.

Also this scenario is observed when running on Virtual Machines even though you have a cool CPU. But i have the same opinion that all instructions should be enabled but...

@error256 'm not sure about that for 100%. I do know that you won't be able to use XSAVE if using Hyper-V and also know that it's possible (at least...