https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102344
--- Comment #3 from Gaius Mulley <gaiusmod2 at gmail dot com> --- "ro at gcc dot gnu.org" <gcc-bugzi...@gcc.gnu.org> writes: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102344 > > Bug ID: 102344 > Summary: gm2/pim/fail/TestLong4.mod FAILs > Product: gcc > Version: 12.0 > Status: UNCONFIRMED > Severity: normal > Priority: P3 > Component: modula2 > Assignee: unassigned at gcc dot gnu.org > Reporter: ro at gcc dot gnu.org > CC: gaiusmod2 at gmail dot com > Target Milestone: --- > > The gm2/pim/fail/TestLong4.mod test FAILs everywhere, it seems (seen on > i386-pc-solaris2.11 and x86_64-pc-linux-gnu, both 32 and 64-bit): > > FAIL: gm2/pim/fail/TestLong4.mod, -g > FAIL: gm2/pim/fail/TestLong4.mod, -O > FAIL: gm2/pim/fail/TestLong4.mod, -O -g > FAIL: gm2/pim/fail/TestLong4.mod, -Os > FAIL: gm2/pim/fail/TestLong4.mod, -O3 -fomit-frame-pointer > FAIL: gm2/pim/fail/TestLong4.mod, -O3 -fomit-frame-pointer -finline-functions > > The test is expected to FAIL, it seems, but actually compilation completes > without error. So this should actually be an XPASS instead. apologies if this is the wrong way to mention a status change. (Is this done on bugzilla? I've looked and cannot see how to change its status :-). I'd like to confirm the bug and report that it is now fixed (I believe) in the git repro. I've moved TestLong4.mod to the pass directory, regards, Gaius regards, Gaius
