public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/89224] [10/11/12 Regression] subscript of const vector has the wrong type Date: Fri, 27 May 2022 09:49:33 +0000 [thread overview] Message-ID: <bug-89224-4-jCGZqs4Qf8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89224-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89224 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|9.5 |10.4 Summary|[9/10/11/12 Regregression] |[10/11/12 Regression] |subscript of const vector |subscript of const vector |has the wrong type |has the wrong type --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- GCC 9 branch is being closed.
next prev parent reply other threads:[~2022-05-27 9:49 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89224-4@http.gcc.gnu.org/bugzilla/> 2021-08-16 20:48 ` [Bug c++/89224] subscript of const vector is considered a rvalue pinskia at gcc dot gnu.org 2021-08-16 20:49 ` [Bug c++/89224] [9/10/11/12 Regregression] " pinskia at gcc dot gnu.org 2021-08-16 20:50 ` pinskia at gcc dot gnu.org 2021-08-16 20:52 ` [Bug c++/89224] [9/10/11/12 Regregression] subscript of const vector has the wrong type pinskia at gcc dot gnu.org 2021-08-16 20:54 ` pinskia at gcc dot gnu.org 2021-08-16 20:56 ` pinskia at gcc dot gnu.org 2021-08-16 20:57 ` pinskia at gcc dot gnu.org 2022-05-27 9:49 ` rguenth at gcc dot gnu.org [this message] 2022-06-28 10:36 ` [Bug c++/89224] [10/11/12 Regression] " jakub at gcc dot gnu.org 2022-07-26 13:49 ` rguenth at gcc dot gnu.org 2022-10-19 9:08 ` [Bug c++/89224] [10/11/12/13 " rguenth at gcc dot gnu.org 2023-07-07 10:34 ` [Bug c++/89224] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-02-20 21:29 ` pinskia at gcc dot gnu.org 2024-02-20 21:35 ` pinskia at gcc dot gnu.org 2024-02-20 22:20 ` pinskia at gcc dot gnu.org 2024-02-20 22:29 ` pinskia at gcc dot gnu.org 2024-02-21 3:07 ` pinskia at gcc dot gnu.org 2024-05-07 22:42 ` [Bug c++/89224] [11/12/13/14/15 " cvs-commit at gcc dot gnu.org 2024-05-07 22:45 ` pinskia at gcc dot gnu.org 2024-05-07 23:50 ` cvs-commit at gcc dot gnu.org 2024-05-08 1:19 ` cvs-commit at gcc dot gnu.org 2024-05-08 2:23 ` cvs-commit at gcc dot gnu.org 2024-05-08 3:19 ` cvs-commit at gcc dot gnu.org 2024-05-08 3:20 ` pinskia at gcc dot gnu.org 2024-05-09 9:21 ` cvs-commit at gcc dot gnu.org 2024-05-09 9:22 ` cvs-commit at gcc dot gnu.org 2024-05-09 9:23 ` cvs-commit at gcc dot gnu.org 2024-05-09 9:24 ` cvs-commit at gcc dot gnu.org 2024-05-09 9:24 ` cvs-commit 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-89224-4-jCGZqs4Qf8@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).