On Sun, Jan 13, 2019 at 11:28:00PM +0100, Thomas Koenig wrote: > > the attached patch adds a -fwrite-module-files options, but the main > point is that it adds its opposite, -fno-write-module-files. > > This has advantages in parallel compiling, as it is quite fast to > generate a module file with -fsyntax-only, and a subsequent > compilation with -fno-write-module-files will not overwrite this.
A worker checks out a copy of the code from the community source repository. At the same time, her coworker checks the same revision. She then works for a week on the project and adds new public routines to a module. She checks her work into the master repositrory. Meanwhile, her coworker used -fsyntax-only to generate module files, and then added the -fno-write-module-files option in his local Makefiles. He now syncs his local sources with the repository. If -fno-write-module-files prevents writing a module file, how do the new interfaces magically appear. There isn't a magic bullet for proper dependencies with parallel compiling. -- Steve
