https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77966
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> --- Yes, the reason is that aggressive loop optimizations are disabled if a -fsanitize is enabled. If you want to catch the out of bounds access to wq_lock array, you can use -fsanitize=undefined.
