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++/113789] [13/14 Regression] ICE on P2266/C++23 `decltype(throw x)` where x is move-eligible parameter
Date: Fri, 16 Feb 2024 17:09:30 +0000	[thread overview]
Message-ID: <bug-113789-4-4YgrDKrjCs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113789-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from GCC 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:254ff3d0e34835b4de93d5e5763a7366dc7d989d

commit r14-9034-g254ff3d0e34835b4de93d5e5763a7366dc7d989d
Author: Marek Polacek <polacek@redhat.com>
Date:   Wed Feb 14 17:53:52 2024 -0500

    c++: implicit move with throw [PR113853]

    Here we have

      template<class T>
      auto is_throwable(T t) -> decltype(throw t, true) { ... }

    where we didn't properly mark 't' as IMPLICIT_RVALUE_P, which caused
    the wrong overload to have been chosen.  Jason figured out it's because
    we don't correctly implement [expr.prim.id.unqual]#4.2, which post-P2266
    says that an id-expression is move-eligible if

    "the id-expression (possibly parenthesized) is the operand of
    a throw-expression, and names an implicitly movable entity that belongs
    to a scope that does not contain the compound-statement of the innermost
    lambda-expression, try-block, or function-try-block (if any) whose
    compound-statement or ctor-initializer contains the throw-expression."

    I worked out that it's trying to say that given

      struct X {
        X();
        X(const X&);
        X(X&&) = delete;
      };

    the following should fail: the scope of the throw is an sk_try, and it's
    also x's scope S, and S "does not contain the compound-statement of the
    *try-block" so x is move-eligible, so we move, so we fail.

      void f ()
      try {
        X x;
        throw x;  // use of deleted function
      } catch (...) {
      }

    Whereas here:

      void g (X x)
      try {
        throw x;
      } catch (...) {
      }

    the throw is again in an sk_try, but x's scope is an sk_function_parms
    which *does* contain the {} of the *try-block, so x is not move-eligible,
    so we don't move, so we use X(const X&), and the code is fine.

    The current code also doesn't seem to handle

      void h (X x) {
        void z (decltype(throw x, true));
      }

    where there's no enclosing lambda or sk_try so we should move.

    I'm not doing anything about lambdas because we shouldn't reach the
    code at the end of the function: the DECL_HAS_VALUE_EXPR_P check
    shouldn't let us go further.

            PR c++/113789
            PR c++/113853

    gcc/cp/ChangeLog:

            * typeck.cc (treat_lvalue_as_rvalue_p): Update code to better
            reflect [expr.prim.id.unqual]#4.2.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/sfinae69.C: Remove dg-bogus.
            * g++.dg/cpp0x/sfinae70.C: New test.
            * g++.dg/cpp0x/sfinae71.C: New test.
            * g++.dg/cpp0x/sfinae72.C: New test.
            * g++.dg/cpp2a/implicit-move4.C: New test.

  parent reply	other threads:[~2024-02-16 17:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 17:51 [Bug c++/113789] New: " arthur.j.odwyer at gmail dot com
2024-02-06 17:59 ` [Bug c++/113789] " pinskia at gcc dot gnu.org
2024-02-06 18:16 ` mpolacek at gcc dot gnu.org
2024-02-06 18:16 ` [Bug c++/113789] [13/14 Regression] " mpolacek at gcc dot gnu.org
2024-02-06 20:32 ` mpolacek at gcc dot gnu.org
2024-02-06 22:32 ` mpolacek at gcc dot gnu.org
2024-02-06 22:32 ` mpolacek at gcc dot gnu.org
2024-02-07  4:35 ` arthur.j.odwyer at gmail dot com
2024-02-10 15:26 ` mpolacek at gcc dot gnu.org
2024-02-16 17:09 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-16 17:14 ` [Bug c++/113789] [13 " mpolacek at gcc dot gnu.org
2024-02-16 17:53 ` arthur.j.odwyer at gmail 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-113789-4-4YgrDKrjCs@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).