https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102344
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
Uni-Bielefeld.DE> ---
> --- Comment #3 from Gaius Mulley <gaiusmod2 at gmail dot com> ---
> 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
> :-).
The customary way is to change the Status to CONFIRMED once you've
verified the report is correct. Once you start working on a fix (or
intend to), assign the PR to yourself. When the fix is done and has
been committed, change the Status to RESOLVED. Please add a PR
reference for the fix to the ChangeLog entry as described in
https://gcc.gnu.org/codingconventions.html#ChangeLogs
e.g
PR modula2/102344
This way, the PR is automatically updated with a reference to the commit.
> 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,
Thanks. I'll try another build of the branch once I get around to it.
