public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "boris at kolpackov dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/100115] Bogus -Wmaybe-uninitialized warning with -O3 Date: Sat, 17 Apr 2021 13:29:05 +0000 [thread overview] Message-ID: <bug-100115-4-9uDIZ4wzB0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100115-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100115 --- Comment #2 from Boris Kolpackov <boris at kolpackov dot net> --- > I'm trying to reduce the test case to something manageable but that can take many hours, even days. Right. On our side we have spent hours, even days trying to suppress this warning (both by rearranging the code and with #pragma) but it keep popping up in different places and on different targets (MinGW, Mac OS, etc). In fact, we've wasted so much time on chasing this (and similar issues in the past), that I am seriously considering just globally disabling this warning since it seems more trouble than it's worth. Sorry, just venting a bit here... > It would be really helpful if you could trim it down a bit, e.g., by removing the biggest non-essentials like <iostream>. I will try. The thing is, such simplifications often make the warning disappear. We have tens of similar code fragments in our codebase, but only this one triggers a warning on x86_64-linux (other places trigger it on MinGW and Mac OS). > That being said, the context of the warning mentions std::optional which has been known to be challenging for analysis [...] Yes, I can confirm that most of the issues with this warning we've encountered in the past involved std::optional.
next prev parent reply other threads:[~2021-04-17 13:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 13:59 [Bug c++/100115] New: " boris at kolpackov dot net 2021-04-16 16:38 ` [Bug tree-optimization/100115] " msebor at gcc dot gnu.org 2021-04-17 13:29 ` boris at kolpackov dot net [this message] 2021-04-17 22:35 ` msebor 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-100115-4-9uDIZ4wzB0@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).