http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59617
--- Comment #18 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > There is quite some usage of __restrict in gcc.target/i386/ directory. > Why doesn't this problem trigger with e.g. avx2-gather-4.c, which also uses > __restrict? AFAICT there is no scan in avx2-gather-4.c. Also the fact that all the other supported tests pass may be because the __restrict is not needed for the tested optimization (wild guess!-).
