public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alx at kernel dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/112833] Missing warnings on restrict misuse Date: Sun, 03 Dec 2023 17:04:07 +0000 [thread overview] Message-ID: <bug-112833-4-3GOFkccFu4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112833-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112833 --- Comment #1 from Alejandro Colomar <alx at kernel dot org> --- 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 reproducer where the call is fine, but the definition is wrong, and the compiler doesn't realize: $ cat restrict.c #include <string.h> long bogus2_strtol(const char *s, char **restrict ep, int base); int main(void) { char buf[3] = "foo"; char *p = buf; bogus2_strtol(p, &p, -42); } long bogus2_strtol(const char *s, char **restrict ep, int base) { memcpy(*ep, s, 1); return base; } $ gcc -Wall -Wextra restrict.c -fanalyzer $ gcc -Wall -Wextra restrict.c -fanalyzer -O3
prev parent reply other threads:[~2023-12-03 17:04 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-03 16:53 [Bug c/112833] New: " alx at kernel dot org 2023-12-03 17:04 ` alx at kernel dot org [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-112833-4-3GOFkccFu4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).