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++/111544] [14 regression] assignment of read-only location after r14-4111-g6e92a6a2a72d3b Date: Fri, 22 Sep 2023 20:23:37 +0000 [thread overview] Message-ID: <bug-111544-4-y7WiAl5wnj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111544-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111544 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- MemoryManager* const fMemoryManager; So reduced: ``` template <int> struct a { int * const t; void f(); }; template <int n> void a<n>::f() { t = 0; } ``` Yes this is invalid code that GCC accepted before.
next prev parent reply other threads:[~2023-09-22 20:23 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-22 18:59 [Bug other/111544] New: " seurer at gcc dot gnu.org 2023-09-22 19:09 ` [Bug other/111544] " sjames at gcc dot gnu.org 2023-09-22 19:51 ` seurer at gcc dot gnu.org 2023-09-22 20:04 ` [Bug c++/111544] " pinskia at gcc dot gnu.org 2023-09-22 20:11 ` sjames at gcc dot gnu.org 2023-09-22 20:16 ` sjames at gcc dot gnu.org 2023-09-22 20:23 ` pinskia at gcc dot gnu.org [this message] 2023-09-22 20:32 ` pinskia at gcc dot gnu.org 2023-09-22 20:34 ` sjames at gcc dot gnu.org 2023-09-22 20:47 ` sjames at gcc dot gnu.org 2023-09-22 21:00 ` pinskia at gcc dot gnu.org 2023-09-22 21:17 ` seurer at gcc dot gnu.org 2023-09-24 9:41 ` redi at gcc dot gnu.org 2023-09-24 9:41 ` redi at gcc dot gnu.org 2023-10-10 17:49 ` seurer at gcc dot gnu.org 2024-01-17 17:53 ` sjames 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-111544-4-y7WiAl5wnj@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).