[Bug c/112833] Missing warnings on restrict misuse

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112833 --- Comment #5 from Alejandro Colomar --- (In reply to Sam James from comment #4) > Mind filing another bug with that? Thanks. I found . It resulted in adding -Wanalyzer-overlapping-buffers,

[Bug c/112833] Missing warnings on restrict misuse

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112833 Sam James changed: What|Removed |Added CC||sjames at gcc dot gnu.org --- Comment #4

[Bug c/112833] Missing warnings on restrict misuse

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112833 --- Comment #3 from Alejandro Colomar --- (In reply to Sam James from comment #2) > Does the analyser have any sort of restrict checks? AFAIK it doesn't. I guess that's a bug (or wishlist) in itself. The `restrict` qualifier is all about data

[Bug c/112833] Missing warnings on restrict misuse

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112833 Sam James changed: What|Removed |Added Component|analyzer|c --- Comment #2 from Sam James --- Does

[Bug c/112833] Missing warnings on restrict misuse

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112833 --- Comment #1 from Alejandro Colomar --- Oops, in the reproducer from above, I should only expect a warning at call site. The definition is correct, since all parameters are restrict, so it's free to copy one to the other. Here's a