Creation of foo.bmi is a byproduct of the compilation of foo.cpp. When compiling foo.cpp, the compiler will emit a foo.o and foo.bmi. As a consequence of this design, foo.cpp must be compiled before bar.cpp!
And implicitly go on to conclude that this prevents them being processed in parallel.
It's not clear to me why the first statement in this line of reasoning has to be true. Can foo.bmi instead be a direct product of compiling foo.hpp? In that case, the comparison is then between:
in parallel:
compile foo.cpp which includes foo.hpp
compile bar.cpp which includes foo.hpp
in parallel:
compile foo.cpp which includes foo.hpp
in sequence:
compile foo.hpp -> foo.bmi
compile bar.cpp
which doesn't seem like a net change in parallelization to me.
As I understand it, in the module proposal, there is no .hpp. You export something from one .cpp with the export keyword and import it into another with the import keyword, not with a #include. The .bmi in the article is basically a magic .hpp generated by the compiler, but the point is that it *must* be generated by processing the .cpp that defines the exported module.
n4720 10.7.1.2 seems to distinguish between a "module interface unit" and a "module implementation unit". This sure sounds like the same distinction that hpp and cpp files currently hold, where one contains declarations, while the other contains their definitions.
13
u/r0b0t1c1st Jan 28 '19 edited Jan 28 '19
You say,
And implicitly go on to conclude that this prevents them being processed in parallel.
It's not clear to me why the first statement in this line of reasoning has to be true. Can
foo.bmiinstead be a direct product of compilingfoo.hpp? In that case, the comparison is then between:in parallel:
compile
foo.cppwhich includesfoo.hppcompile
bar.cppwhich includesfoo.hppin parallel:
compile
foo.cppwhich includesfoo.hppin sequence:
compile
foo.hpp->foo.bmicompile
bar.cppwhich doesn't seem like a net change in parallelization to me.