On 12/06/2017 12:58 PM, Martin Sebor wrote: > On 12/06/2017 12:41 PM, Jeff Law wrote: >> On 12/06/2017 12:27 PM, Martin Sebor wrote: >>> For reference, I committed r255450 to avoid the test failure >>> reported on the arm-none-eabi target. The warning is valid >>> but unrelated to the purpose of the test so I pruned it from >>> its output. >>> >>> Martin >>> >>> Index: gcc/testsuite/ChangeLog >>> =================================================================== >>> --- gcc/testsuite/ChangeLog (revision 255449) >>> +++ gcc/testsuite/ChangeLog (working copy) >>> @@ -9,6 +9,9 @@ >>> >>> 2017-12-06 Martin Sebor <mse...@redhat.com> >>> >>> + PR testsuite/83303 >>> + * g++.dg/opt/new1.C: Prune warning from test output. >> The path to the erroneous behavior should be caught and eliminated by >> DOM. That's the whole point behind one of the recent changes. >> >> Instead we need to figure out why it wasn't caught on arm-none-eabi. > > Yes, I should have suggested to look into the failure to do > that, independently of the test. I can open a new bug for > it unless it's already on your to-do list. I think the right thing to do is revert the change and keep 83303 open until we see what's different about arm-none-eabi. I only noticed this because I'd debugged that test on x86_64 and fixed DOM to eliminate the problem path over the weekend... So something is clearly different on that platform.
jeff
