[Bug c/48885] missed optimization with restrict qualifier?

["glisse at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48885

--- Comment #8 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Paulo J. Matos from comment #7)
> There are still a few questions. One is why the standard only uses examples
> where all the pointers are restricted (with the exception example of the one
> you post where the 'c' was extern).

Feel free to contact WG14 to try and get them to add another example, I'd
certainly welcome even a sentence clarifying that one "restrict" is sufficient
in one of the examples.

> The other is why was GCC working
> according to standard (or apparently so in 4.5) and changed in 4.6. Was it
> on purpose or was it on by accident?

I wasn't there, you'd have to check the logs and read the ML archives from that
time.

> If on purpose then this decision to
> deviate from the standard should be documented and this bug can be marked as
> INVALID.

WONTFIX at most, not INVALID.