Hi,
Is it okay to backport 0d24289d129639efdc79338a64188d6d404375e8 to
releases/gcc-13?
Without this backport, I see these failures on arm-none-eabi:
FAIL: g++.dg/warn/Wuse-after-free3.C -std=gnu++14 (test for excess errors)
FAIL: g++.dg/warn/Wuse-after-free3.C -std=gnu++17 (test for excess errors)
FAIL: g++.dg/warn/Wuse-after-free3.C -std=gnu++20 (test for excess errors)
Kind regards,
Torbjörn
On 2023-11-22 09:26, Alexandre Oliva wrote:
On Nov 20, 2023, Jason Merrill <ja...@redhat.com> wrote:
So it only passed on that platform before because of the bug?
I'm not sure it passed (we've had patches for that testcase before), but
I didn't look closely enough into their history to tell. I suspected
the warning suppression machinery changed, or details on cloning did, or
something. It's been fragile historically. But yeah, recently, the
test for the warning was only passing because of the bug. But we were
also getting excess warnings, so it wasn't fully passing.
Thanks for the reviews!
