public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/98484] missing -Wstringop-overflow on invalid accesses to the same object by distinct functions Date: Sun, 26 Sep 2021 09:26:56 +0000 [thread overview] Message-ID: <bug-98484-4-knEnGKtYvA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98484-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98484 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2021-09-26 Ever confirmed|0 |1 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. -Wsystem-headers enables all of the warnings ... What is interesting is in GCC 10, we don't even get the warning for g0 without -Wsystem-headers. In GCC 9 -Wsystem-headers does not enable the warning for g1 or g2 either.
prev parent reply other threads:[~2021-09-26 9:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-30 22:29 [Bug middle-end/98484] New: missing -Wstringop-overflow on a multiply inlined calls from system header msebor at gcc dot gnu.org 2020-12-30 22:43 ` [Bug middle-end/98484] missing -Wstringop-overflow on invalid accesses to the same object by distinct functions msebor at gcc dot gnu.org 2021-09-26 9:26 ` pinskia at gcc dot gnu.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-98484-4-knEnGKtYvA@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).