public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102192] Curious '-O2'-only '-Wmaybe-uninitialized' diagnostics for 'libgomp.oacc-fortran/routine-10.f90' Date: Wed, 06 Oct 2021 16:44:50 +0000 [thread overview] Message-ID: <bug-102192-4-64vkMMIeZq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102192-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102192 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Ever confirmed|0 |1 CC| |msebor at gcc dot gnu.org Last reconfirmed| |2021-10-06 --- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> --- There are lots of reports about -Wmaybe-uninitialized triggering when it's not expected to. Some are bugs/limitations in the warning but others are inherent in the IL the warning works with and can't be avoided given its design. Without a small test case to easily reproduce the suspected problem, given the large number of reports with test cases, it's unlikely that anyone will go try to extract one from a historical Git revision of a test, especially one written in FORTRAN and involving complex control flow, to determine were this one falls. I would suggest to include the test in the bug report, along with the output (as we ask users to do). Better yet would be reducing the suspected false positive to a smaller test case, and ideally converting it to C.
next prev parent reply other threads:[~2021-10-06 16:44 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-03 14:59 [Bug tree-optimization/102192] New: " tschwinge at gcc dot gnu.org 2021-10-06 16:44 ` msebor at gcc dot gnu.org [this message] 2022-01-13 10:52 ` [Bug tree-optimization/102192] " cvs-commit 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-102192-4-64vkMMIeZq@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).