public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103185] [11/12/13 Regression] ind[arr] is rejected when arr is an array prvalue
Date: Wed, 24 Jan 2024 19:39:07 +0000	[thread overview]
Message-ID: <bug-103185-4-negOQZFN0m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103185-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103185

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:

https://gcc.gnu.org/g:fcc06cf83a9571a0745fcde83d955eb7d7f16910

commit r13-8248-gfcc06cf83a9571a0745fcde83d955eb7d7f16910
Author: Jason Merrill <jason@redhat.com>
Date:   Tue Dec 19 16:12:02 2023 -0500

    c++: xvalue array subscript [PR103185]

    Normally we handle xvalue array subscripting with ARRAY_REF, but in this
    case we weren't doing that because the operands were reversed.  Handle that
    case better.

            PR c++/103185

    gcc/cp/ChangeLog:

            * typeck.cc (cp_build_array_ref): Handle swapped operands.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1z/array-prvalue2.C: New test.
            * g++.dg/cpp1z/eval-order3.C: Test swapped operands.

    (cherry picked from commit 8dfc52a75d4d6c8be1c61b4aa831b1812b14a10e)

  parent reply	other threads:[~2024-01-24 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  8:49 [Bug c++/103185] New: " de34 at live dot cn
2023-11-28 17:11 ` [Bug c++/103185] [11/12/13/14 Regression] " ppalka at gcc dot gnu.org
2023-11-28 17:11 ` ppalka at gcc dot gnu.org
2023-12-19 20:58 ` jason at gcc dot gnu.org
2023-12-20 17:31 ` cvs-commit at gcc dot gnu.org
2024-01-24 19:39 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-24 19:40 ` [Bug c++/103185] [11/12/13 " cvs-commit at gcc dot gnu.org
2024-01-24 19:45 ` cvs-commit at gcc dot gnu.org
2024-01-24 19:45 ` jason 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-103185-4-negOQZFN0m@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).