http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59617
--- Comment #19 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Uroš Bizjak from comment #17) > (In reply to Iain Sandoe from comment #14) > > (In reply to Dominique d'Humieres from comment #13) > > > Another option would be to add -std=c99 for darwin. > > > > I would suggest that this is the Right Thing to do. > > 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? presumably, other tests don't include the system header that is the source of the problem (which can be checked). My understanding is that restrict is c99 (and, the addition of -std= was only being proposed for darwin, so other targets would be unaffected) however, that said, I am of course open to other solutions.
