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++/103403] [11/12 Regression] auto return type with a trailing return type of decl(auto) uses rvalue reference type instead of reference type
Date: Fri, 03 Dec 2021 19:00:37 +0000	[thread overview]
Message-ID: <bug-103403-4-UGjBGMbMEs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103403-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

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

commit r12-5778-gabd7712f91c99690f8b0046ea168b2782afbac69
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Nov 30 21:07:25 2021 -0500

    c++: Fix for decltype(auto) and parenthesized expr [PR103403]

    In r11-4758, I tried to fix this problem:

      int &&i = 0;
      decltype(auto) j = i; // should behave like int &&j = i; error

    wherein do_auto_deduction was getting confused with a REFERENCE_REF_P
    and it didn't realize its operand was a name, not an expression, and
    deduced the wrong type.

    Unfortunately that fix broke this:

      int&& r = 1;
      decltype(auto) rr = (r);

    where 'rr' should be 'int &' since '(r)' is an expression, not a name.  But
    because I stripped the INDIRECT_REF with the r11-4758 change, we deduced
    'rr's type as if decltype had gotten a name, resulting in 'int &&'.

    I suspect I thought that the REF_PARENTHESIZED_P check when setting
    'bool id' in do_auto_deduction would handle the (r) case, but that's not
    the case; while the documentation for REF_PARENTHESIZED_P specifically says
    it can be set in INDIRECT_REF, we don't actually do so.

    This patch sets REF_PARENTHESIZED_P even on REFERENCE_REF_P, so that
    do_auto_deduction can use it.

    It also removes code in maybe_undo_parenthesized_ref that I think is
    dead -- and we don't hit it while running dg.exp.  To adduce more data,
    it also looks dead here:
    https://splichal.eu/lcov/gcc/cp/semantics.c.gcov.html
    (It's dead since r9-1417.)

    Also add a fixed test for c++/81176.

            PR c++/103403

    gcc/cp/ChangeLog:

            * cp-gimplify.c (cp_fold): Don't recurse if
maybe_undo_parenthesized_ref
            doesn't change its argument.
            * pt.c (do_auto_deduction): Don't strip REFERENCE_REF_P trees if
they
            are REF_PARENTHESIZED_P.  Use stripped_init when checking for
            id-expression.
            * semantics.c (force_paren_expr): Set REF_PARENTHESIZED_P on
            REFERENCE_REF_P trees too.
            (maybe_undo_parenthesized_ref): Remove dead code.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1y/decltype-auto2.C: New test.
            * g++.dg/cpp1y/decltype-auto3.C: New test.
            * g++.dg/cpp1y/decltype-auto4.C: New test.
            * g++.dg/cpp1z/decomp-decltype1.C: New test.

  parent reply	other threads:[~2021-12-03 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24  9:38 [Bug c++/103403] New: Decltype of rvalue reference enricomaria.dean6elis at gmail dot com
2021-11-24  9:50 ` [Bug c++/103403] " pinskia at gcc dot gnu.org
2021-11-24  9:59 ` [Bug c++/103403] [11/12 Regression] auto return type with a trailing return type of decl(auto) uses rvalue reference type instead of reference type pinskia at gcc dot gnu.org
2021-11-24 10:09 ` rguenth at gcc dot gnu.org
2021-11-24 14:37 ` mpolacek at gcc dot gnu.org
2021-11-24 15:07 ` enricomaria.dean6elis at gmail dot com
2021-12-03 19:00 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-03 19:01 ` [Bug c++/103403] [11 " mpolacek at gcc dot gnu.org
2022-04-21  7:50 ` rguenth at gcc dot gnu.org
2023-03-07 17:46 ` mpolacek 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-103403-4-UGjBGMbMEs@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).