public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105178] [11 Regression] g++ incorrectly reports invalid use of incomplete type Date: Wed, 06 Apr 2022 13:43:25 +0000 [thread overview] Message-ID: <bug-105178-4-9H5hNhFF7D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105178-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105178 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.3 Status|UNCONFIRMED |NEW Keywords| |rejects-valid CC| |ppalka at gcc dot gnu.org Last reconfirmed| |2022-04-06 Ever confirmed|0 |1 Summary|g++ incorrectly reports |[11 Regression] g++ |invalid use of incomplete |incorrectly reports invalid |type |use of incomplete type See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=104242 --- Comment #2 from Patrick Palka <ppalka at gcc dot gnu.org> --- Confirmed, trunk and 11.2.0 accept the testcase. This is likely caused by r11-9303-g853b9d54365372 and the same bug as PR104242 except reported against 11 instead of trunk. I can confirm that backporting r12-7708-g7a42b1fa1a090e to the 11 branch fixes the testcase there.
next prev parent reply other threads:[~2022-04-06 13:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-06 13:01 [Bug c++/105178] New: " oss.abde.sassi at gmail dot com 2022-04-06 13:32 ` [Bug libstdc++/105178] " rguenth at gcc dot gnu.org 2022-04-06 13:43 ` ppalka at gcc dot gnu.org [this message] 2022-04-21 7:51 ` [Bug libstdc++/105178] [11 Regression] " rguenth at gcc dot gnu.org 2023-05-29 10:06 ` jakub at gcc dot gnu.org 2023-06-23 11:40 ` redi at gcc dot gnu.org 2023-06-23 12:57 ` redi 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-105178-4-9H5hNhFF7D@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).