You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the invocation of ftn, any USE statements in the Fortran code will indicate to ftn to locate a .mod file specified in the
directory specified by the flag -J <dir> (-J ./ompvv).
When multiple threads are just to execute the make file, each .mod file created in ./ompvv is subject to a race condition, which leads to module file corruption. Hence, running the testsuite using multiple threads with ftn becomes untenable.
A proposed solution is to do away with .mod file creation, and instead store the module info in the .o file created by ftn.
This can be done by using -dm and removing -J .
The text was updated successfully, but these errors were encountered:
On the invocation of ftn, any USE statements in the Fortran code will indicate to ftn to locate a .mod file specified in the
directory specified by the flag -J <dir> (-J ./ompvv).
When multiple threads are just to execute the make file, each .mod file created in ./ompvv is subject to a race condition, which leads to module file corruption. Hence, running the testsuite using multiple threads with ftn becomes untenable.
A proposed solution is to do away with .mod file creation, and instead store the module info in the .o file created by ftn.
This can be done by using
-dm
and removing-J
.The text was updated successfully, but these errors were encountered: