https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
--- Comment #72 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > "restrict" is not something you apply to a call; it is something the call > applies to you. If a function declares two argument pointers "restrict" and > you pass in overlapping (or identical) memory regions, you are invoking > undefined behavior. Yes, that's this PR, but that was not what I was talking about.
