https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113005
--- Comment #14 from Lipeng Zhu ---
(In reply to Lipeng Zhu from comment #13)
> OK, I think I find the root cause of this error, when thread number greater
> than 1000, the file_name = 1000_tst.dat, character(11) will overflow. This
> will gener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113005
--- Comment #13 from Lipeng Zhu ---
OK, I think I find the root cause of this error, when thread number greater
than 1000, the file_name = 1000_tst.dat, character(11) will overflow. This will
generate the same file_name like ***_tst.dat.
diff
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113005
--- Comment #12 from Lipeng Zhu ---
(In reply to Lipeng Zhu from comment #9)
> Since I still can't reproduce the failure on my side :(, just curious, will
> the new added 'rwlock' test cases failed on mutex lock?
OK, I rerun these rwlock* test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113005
--- Comment #11 from Lipeng Zhu ---
(In reply to Jakub Jelinek from comment #10)
>For what I can reproduce on my box (rwlock_1.exe built in the
>x86_64-pc-linux-gnu/libgomp/testsuite subdirectory using the -O0
>compilation line from libgomp*/*.s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113005
--- Comment #9 from Lipeng Zhu ---
Since I still can't reproduce the failure on my side :(, just curious, will the
new added 'rwlock' test cases failed on mutex lock?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113005
Lipeng Zhu changed:
What|Removed |Added
CC||lipeng.zhu at intel dot com
--- Comment #4
