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 tree-optimization/109968] False Warning stringop-overread when -O2 and -fsanitize=address used Date: Thu, 25 May 2023 16:23:46 +0000 [thread overview] Message-ID: <bug-109968-4-AmBzhQbRoe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109968-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109968 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- From https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Instrumentation-Options.html#index-fsanitize_003daddress : Note that sanitizers tend to increase the rate of false positive warnings, most notably those around -Wmaybe-uninitialized. We recommend against combining -Werror and [the use of] sanitizers.
next prev parent reply other threads:[~2023-05-25 16:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-25 16:09 [Bug c/109968] New: " davekelly13 at gmail dot com 2023-05-25 16:23 ` pinskia at gcc dot gnu.org [this message] 2023-05-25 16:54 ` [Bug tree-optimization/109968] False Warning stringop-overread at -O2 pinskia at gcc dot gnu.org 2023-05-25 16:55 ` pinskia at gcc dot gnu.org 2023-05-26 6:08 ` rguenth at gcc dot gnu.org
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-109968-4-AmBzhQbRoe@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).