This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/81195] SPEC CPU2017 621.wrf_s failure with 40+ openmp threads
- From: "wilson at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 24 Jun 2017 20:16:46 +0000
- Subject: [Bug libfortran/81195] SPEC CPU2017 621.wrf_s failure with 40+ openmp threads
- Auto-submitted: auto-generated
- References: <bug-81195-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81195
--- Comment #6 from Jim Wilson <wilson at gcc dot gnu.org> ---
I should point out that there are currently four places that use
newunit_stack/newunit_tos without locking. Two of these places required
locking code to get wrf working.
The other two are init_units and close_units. These are called from a
constructor and a destructor. Presumably these can only be called once, and
hence don't require locking code. Though curiously, close_units has some
locking code anyways. I'm not sure why. I saw no failures here, and hence
didn't bother to add any locking.