public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alvaro.begue at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108667] Spurious "may be used uninitialized [-Wmaybe-uninitialized]" warning Date: Sat, 04 Feb 2023 00:33:30 +0000 [thread overview] Message-ID: <bug-108667-4-qFk3F3zAOb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108667-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108667 --- Comment #2 from Alvaro Begue <alvaro.begue at gmail dot com> --- Yes, this is a reduction of real code. I'm writing a signal class and I wrote a small test for it. It worked fine when compiling unoptimized, but the optimized version gave me this odd warning. Would it be interesting to see the original code? It's only around 50 lines of code.
next prev parent reply other threads:[~2023-02-04 0:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-03 22:02 [Bug c++/108667] New: Spurious "maybe " alvaro.begue at gmail dot com 2023-02-04 0:07 ` [Bug tree-optimization/108667] Spurious "may be " pinskia at gcc dot gnu.org 2023-02-04 0:33 ` alvaro.begue at gmail dot com [this message] 2023-02-06 7:47 ` rguenth at gcc dot gnu.org 2023-02-06 15:19 ` alvaro.begue at gmail dot com
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-108667-4-qFk3F3zAOb@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).