[Bug default/20365] suppress apparently harmless restrict type qualification change

["woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=20365

--- Comment #4 from Ben Woodard <woodard at redhat dot com> ---
This discussion was with Dodji. He pointed out that C++ function mangling and
the C++ function matching remain the same despite the addition or loss of
restrict qualifier. This differs markedly in comparison to the const qualifier
which leads to a different function fingerprint.

Personally, I remain somewhat unconvinced but have no counter arguments.
Unequipped with any arguments my position is that we should document the
decision and if someone argues with it as you apparently are, then we discuss
it further taking it all the way to the language standards bodies or the
maintainers of the ABI standard if necessary.

Also, if at some point in the future we discover a case where the addition or
removal of restrict does impact run time linking between objects then the issue
most likely should be specified either in the language or the ABI for the
platform.

-- 
You are receiving this mail because:
You are on the CC list for the bug.