[Bug other/99903] 32-bit x86 frontends randomly crash while reporting timing on Windows

2021-05-04 Thread amonakov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99903 Alexander Monakov changed: What|Removed |Added Ever confirmed|1 |0 Status|WAITING

[Bug other/99903] 32-bit x86 frontends randomly crash while reporting timing on Windows

2021-04-06 Thread izbyshev at ispras dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99903 --- Comment #3 from Alexey Izbyshev --- Crashes eventually occurred with both one- and two-processor affinity masks, so pinning GCC to a single core doesn't help. But I've tracked the reason down. When `get_time()` from `gcc/timevar.c` gets

[Bug other/99903] 32-bit x86 frontends randomly crash while reporting timing on Windows

2021-04-04 Thread izbyshev at ispras dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99903 --- Comment #2 from Alexey Izbyshev --- > Is there a way to bind GCC to a specific core and test again? Yes, `repro.py` can be run via `start /affinity MASK`. I've started two experiments, with one- and two-processor masks. They haven't crashed

[Bug other/99903] 32-bit x86 frontends randomly crash while reporting timing on Windows

2021-04-04 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99903 Andrew Pinski changed: What|Removed |Added Build|i686-w64-mingw32| Status|UNCONFIRMED