public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103347] Non-static data member initialization is erroneously allowed in C++03 mode Date: Mon, 22 Nov 2021 09:47:18 +0000 [thread overview] Message-ID: <bug-103347-4-APxnjvEFKo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103347-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103347 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |--- Status|RESOLVED |NEW Last reconfirmed| |2021-11-22 Ever confirmed|0 |1 --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Actually let's reopen this one too. It might be a different bug from PR 77299 ...
next prev parent reply other threads:[~2021-11-22 9:47 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-21 12:13 [Bug c++/103347] New: " fchelnokov at gmail dot com 2021-11-21 14:50 ` [Bug c++/103347] " pinskia at gcc dot gnu.org 2021-11-21 14:52 ` pinskia at gcc dot gnu.org 2021-11-21 14:54 ` pinskia at gcc dot gnu.org 2021-11-21 17:02 ` redi at gcc dot gnu.org 2021-11-22 9:37 ` pinskia at gcc dot gnu.org 2021-11-22 9:38 ` pinskia at gcc dot gnu.org 2021-11-22 9:47 ` pinskia at gcc dot gnu.org [this message] 2021-11-22 9:53 ` [Bug c++/103347] [9/10/11/12 Regression] Non-static data member initialization is erroneously allowed in C++03 with assignment to NULL pinskia at gcc dot gnu.org 2021-11-22 16:43 ` jakub at gcc dot gnu.org 2021-11-22 18:19 ` mpolacek at gcc dot gnu.org 2021-11-24 5:24 ` cvs-commit at gcc dot gnu.org 2021-11-24 5:26 ` [Bug c++/103347] [9/10/11 " mpolacek at gcc dot gnu.org 2021-12-01 2:51 ` ensadc at mailnesia 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-103347-4-APxnjvEFKo@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).