https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118763
--- Comment #11 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Jakub Jelinek <ja...@gcc.gnu.org>: https://gcc.gnu.org/g:7cb46536f7aabdb43e69dc9b21471366f18026ae commit r13-9589-g7cb46536f7aabdb43e69dc9b21471366f18026ae Author: Jakub Jelinek <ja...@redhat.com> Date: Fri Feb 7 14:30:11 2025 +0100 c++: Don't use CLEANUP_EH_ONLY for new expression cleanup [PR118763] The following testcase is miscompiled since r12-6325 stopped preevaluating the initializers for new expression. If evaluating the initializers throws, there is a correct cleanup for that, but it is marked CLEANUP_EH_ONLY. While in standard C++ that is just fine, if it has statement expressions, it can return or goto out of the expression and we should delete the pointer in that case too. There is already a sentry variable initialized to true and set to false after everything is initialized and used as a guard for the cleanup, so just removing the CLEANUP_EH_ONLY flag does everything we need. And in the normal case of the initializer not using statement expressions at least with -O2 we get the same code, while the change changes one try { sentry = true; ... sentry = false; } catch { if (sentry) delete ...; } into try { sentry = true; ... sentry = false; } finally { if (sentry) delete ...; } optimizations will see that sentry is false when reaching the finally other than through an exception. Though, wonder what other CLEANUP_EH_ONLY cleanups might be an issue with statement expressions. 2025-02-07 Jakub Jelinek <ja...@redhat.com> PR c++/118763 * init.cc (build_new_1): Don't set CLEANUP_EH_ONLY. * g++.dg/asan/pr118763.C: New test. (cherry picked from commit fcecc74cb38723457a0447924d9993b31252a8f9)
