Here our named return value optimization was breaking the required
destructor when the goto takes 'a' out of scope. The simplest fix is to
disable the optimization in the presence of user labels.
We could do better by disabling the optimization only if there is a backward
goto across the variable declaration, but we don't currently track that.
PR c++/92407
gcc/cp/ChangeLog:
* typeck.cc (check_return_expr): Prevent NRV in the presence of
named labels.
gcc/testsuite/ChangeLog:
* g++.dg/opt/nrv22.C: New test.
if (fn_returns_value_p && flag_elide_constructors)
{
if (named_return_value_okay_p
+ /* The current NRV implementation breaks if a backward goto needs to
+ destroy the object (PR92407). */
+ && !cp_function_chain->x_named_labels
&& (current_function_return_value == NULL_TREE
|| current_function_return_value == bare_retval))
current_function_return_value = bare_retval;
--- /dev/null
+// PR c++/92407
+// { dg-do run }
+
+struct A
+{
+ A () { a++; }
+ A (const A &) { a++; }
+ ~A () { a--; }
+ static int a;
+};
+int A::a = 0;
+
+A
+foo ()
+{
+ int cnt = 10;
+lab:
+ A a;
+ if (cnt--)
+ goto lab;
+ return a;
+}
+
+int
+main ()
+{
+ foo ();
+ if (A::a)
+ __builtin_abort ();
+}