Hi, Thanks for checking the history.
On Sun, Apr 12, 2020 at 01:50:12PM +0200, Bill Allombert wrote: > > Is this stil an issue with the newer versions of gcc-mingw-w64? > > > > Should this bug really be marked as serious? > > Please note that I reported the bug as severity normal but Stephen bumped it > to serious, maybe due to the release. I know (sorry that wasn't clear in my previous mail). > Fortunately I forgot to remove my old logs. > > - my setup reported failure up to March 14 2019 when I switched to gcc > 6.3.0 to avoid the issue. > - I upgraded the box on March 24 2020 to gcc version 8.3-win32 20190406 (GCC) > which passes the test. > - I just tested with 9.3-posix 20200324 and this passes the test too. > > I very much like to see a chaangelog that tell what changed betwee 8.2 > and 8.3 that could have fixed this. So I guess the current version in testing is ok, and the bug can be closed there? If it works on gcc 8.3, does that mean it works with the version in stable as well? The current version in stable was built wit gcc 8.3.0-6. Cheers, Ivo
