public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94905] [10 Regression] Bogus warning -Werror=maybe-uninitialized
Date: Thu, 03 Sep 2020 18:46:43 +0000 [thread overview]
Message-ID: <bug-94905-4-eZaWuSwyEs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94905-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Bogus warning |[10 Regression] Bogus
|-Werror=maybe-uninitialized |warning
| |-Werror=maybe-uninitialized
Target Milestone|--- |10.4
Ever confirmed|0 |1
Last reconfirmed| |2020-09-03
Status|UNCONFIRMED |NEW
--- Comment #10 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #3)
> The best I've been able to come up with is the following, reduced from APL
> 1.8:
It is warning about this, but it should not warn:
# DEBUG rD.2406 => (intD.9) (ivtmp.24_6 /[ex] 4) + 1
[./example.cpp:8:27] # VUSE <.MEM_11>
pretmp_8 = MEM[(intD.9 *)&retD.2381 + ivtmp.24_13 * 1];
This is regression but not sure when it was introduced.
next prev parent reply other threads:[~2020-09-03 18:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 16:25 [Bug c++/94905] New: " bug-apl at gnu dot org
2020-05-01 22:41 ` [Bug c++/94905] " glisse at gcc dot gnu.org
2020-05-03 13:28 ` bug-apl at gnu dot org
2020-05-03 15:02 ` asolokha at gmx dot com
2020-05-03 16:10 ` bug-apl at gnu dot org
2020-05-03 16:16 ` bug-apl at gnu dot org
2020-05-03 16:26 ` asolokha at gmx dot com
2020-07-02 15:47 ` moller at mollerware dot com
2020-07-02 15:51 ` moller at mollerware dot com
2020-09-03 18:34 ` manu at gcc dot gnu.org
2020-09-03 18:46 ` manu at gcc dot gnu.org [this message]
2021-04-08 16:34 ` [Bug tree-optimization/94905] [10/11 Regression] " jason at gcc dot gnu.org
2022-01-21 13:41 ` rguenth at gcc dot gnu.org
2022-01-21 13:41 ` rguenth at gcc dot gnu.org
2022-01-21 13:43 ` rguenth at gcc dot gnu.org
2022-01-31 14:50 ` marxin at gcc dot gnu.org
2022-04-07 9:39 ` rguenth at gcc dot gnu.org
2022-04-07 10:01 ` jakub at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2023-07-07 10:37 ` [Bug tree-optimization/94905] [11 " 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-94905-4-eZaWuSwyEs@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: link
Be 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).