public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Marek Polacek <mpolacek@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-3277] c++: ICE with VEC_INIT_EXPR and defarg [PR106925]
Date: Thu, 13 Oct 2022 15:06:14 +0000 (GMT)	[thread overview]
Message-ID: <20221013150614.125103858C55@sourceware.org> (raw)

https://gcc.gnu.org/g:3130e70dab1e64a7b014391fe941090d5f3b6b7d

commit r13-3277-g3130e70dab1e64a7b014391fe941090d5f3b6b7d
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Oct 11 14:16:54 2022 -0400

    c++: ICE with VEC_INIT_EXPR and defarg [PR106925]
    
    Since r12-8066, in cxx_eval_vec_init we perform expand_vec_init_expr
    while processing the default argument in this test.  At this point
    start_preparsed_function hasn't yet set current_function_decl.
    expand_vec_init_expr then leads to maybe_splice_retval_cleanup which
    checks DECL_CONSTRUCTOR_P (current_function_decl) without checking that
    c_f_d is non-null first.  It seems correct that c_f_d is null here, so
    it seems to me that maybe_splice_retval_cleanup should check c_f_d as
    in the following patch.
    
            PR c++/106925
    
    gcc/cp/ChangeLog:
    
            * except.cc (maybe_splice_retval_cleanup): Check current_function_decl.
            Make the bool const.
    
    gcc/testsuite/ChangeLog:
    
            * g++.dg/cpp0x/initlist-defarg3.C: New test.

Diff:
---
 gcc/cp/except.cc                              |  7 +++++--
 gcc/testsuite/g++.dg/cpp0x/initlist-defarg3.C | 13 +++++++++++++
 2 files changed, 18 insertions(+), 2 deletions(-)

diff --git a/gcc/cp/except.cc b/gcc/cp/except.cc
index 703d1d566c9..2677a9b7678 100644
--- a/gcc/cp/except.cc
+++ b/gcc/cp/except.cc
@@ -1307,9 +1307,12 @@ maybe_splice_retval_cleanup (tree compound_stmt)
 {
   /* If we need a cleanup for the return value, add it in at the same level as
      pushdecl_outermost_localscope.  And also in try blocks.  */
-  bool function_body
+  const bool function_body
     = (current_binding_level->level_chain
-       && current_binding_level->level_chain->kind == sk_function_parms);
+       && current_binding_level->level_chain->kind == sk_function_parms
+      /* When we're processing a default argument, c_f_d may not have been
+	 set.  */
+       && current_function_decl);
 
   if ((function_body || current_binding_level->kind == sk_try)
       && !DECL_CONSTRUCTOR_P (current_function_decl)
diff --git a/gcc/testsuite/g++.dg/cpp0x/initlist-defarg3.C b/gcc/testsuite/g++.dg/cpp0x/initlist-defarg3.C
new file mode 100644
index 00000000000..5c3e886b306
--- /dev/null
+++ b/gcc/testsuite/g++.dg/cpp0x/initlist-defarg3.C
@@ -0,0 +1,13 @@
+// PR c++/106925
+// { dg-do compile { target c++11 } }
+
+struct Foo;
+template <int _Nm> struct __array_traits { typedef Foo _Type[_Nm]; };
+template <int _Nm> struct array {
+  typename __array_traits<_Nm>::_Type _M_elems;
+};
+template <int size> struct MyVector { array<size> data{}; };
+struct Foo {
+  float a{0};
+};
+void foo(MyVector<1> = MyVector<1>());

                 reply	other threads:[~2022-10-13 15:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221013150614.125103858C55@sourceware.org \
    --to=mpolacek@gcc.gnu.org \
    --cc=gcc-cvs@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).