https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127518
--- Comment #3 from Huazhao Chen <lyican53 at sjtu dot edu.cn> --- I ran the testcase through every point release available in the gcc docker images (same testcase, same options, -O2 -Wall -Wextra), and the results were: fires: 11.3.0, 12.5.0, 13.1.0, 13.2.0, 14.1.0, 14.2.0, 14.3.0, 14.4.0 clean: 13.3.0, 13.4.0, 15.3.0 So the warning is still there in 13.1 and 13.2, gone from 13.3 onwards, and 15 is clean too, but every 14.x release I tried still fires. Looks like the fix landed on mainline somewhere between the 14 branch point and 13.3, was backported to 13 for 13.3, and simply never made it to the 14 branch. If so, this is a missing backport to releases/gcc-14 rather than a new regression.
