[cfe-dev] Modules TS Work
David Blaikie via cfe-dev
cfe-dev at lists.llvm.org
Mon Oct 15 08:30:46 PDT 2018
On Sat, Oct 13, 2018 at 4:41 AM Whisperity <whisperity at gmail.com> wrote:
> As I have now delved a bit into the Modules TS implementation from a
> user standpoint (due to having implemented support for it in CMake,
> see the patch here:
> https://gitlab.kitware.com/cmake/cmake/merge_requests/2482 )
> (Some of these concerns are already voiced by Boris in
> https://build2.org/article/cxx-modules-misconceptions.xhtml#build )
> 1. The first big issue is that while the "C++98 Modules" is somewhat
> well-documented, the "Modules TS" has absolutely no workable
> documentation available at all... I had to resort to looking up
> Clang's option td files to figure out what this thing is supposed to
Fair cop - work in progress, etc. Though it's far enough along it could
probably use some documentation even if it said clearly "this is in flux,
may be out of date, etc".
> 2. Currently, Clang is wonky on how modules can be found. You need to
> explicitly specify the modules' location which (the prebuilt, if you
> want to allow caching of PCMs and no re-read of CPPM files all the
> time...) has to be a single folder.
What command line are you referring to here? -fmodule-cache-path?
That's more used around the "implicit modules" support, which isn't likely
to be supported/useful for ModulesTS style modules (becaues you'll want,
maybe need, to build object files from the module files - so your build
system would need to be aware of building module files).
> The PCM must be available prior to
> compilation so the main file is semantically correct, but *it also has
> to be linked* against the resulting binary, otherwise implementations
> will provide linker errors. (If I link .o instead of .pcm, it will
> still work, and .o files are smaller than PCMs, but compilation will
> have to semantically analyse the CPPM file providing no speedup on
> module contents.) There is no direct sanity check that I'm linking the
> same PCM that I used for compiling, and it looks like the PCM must be
> linked *explicitly* (so the '-fprebuilt-modules-path' doesn't work
yep, the build model currently is entirely explicit, something like this
COMMON_FLAGS="-cc1 -xc++ -emit-module -fmodules -w"
$CLANG $COMMON_FLAGS -fmodule-name=foo foo.cppmap -o foo.pcm
$CLANG $COMMON_FLAGS -fmodule-name=bar bar.cppmap -o bar.pcm
$CLANG -c foo.pcm
$CLANG -c bar.pcm
$CLANG -cc1 -emit-obj -fmodules -fmodule-file=foo.pcm -fmodule-file=bar.pcm
$CLANG foo.o bar.o use.o
Basically - build the .pcms, use those pcms to build object files for the
pcms, and use the pcms to help build the object file for the user, then
link all the objects together as usual.
3. This might be very CMake specific or I only found this issue
> because working on CMake recently, but it is a real pain the behind to
> figure out on which modules a translation unit depends. Unlike '-M'
> which nicely spits out imports, the only option I saw so far is to
> grep for the import statements and then try to map these to the module
> files under the prebuild folder. (This is one of the issues I just
> didn't succeed (perhaps yet?) in CMake because CMake is also
> *somewhat* wonky, at dependency check time it does not know about
> other targets and configuration, so I just can't implictly and
> automatically say "Okay now please depend on
> ./whatever/path/mymodule.pcm or it's corresponding cppm input...)
> I think this eventually needs to be considered because -M respects
> compiler options when resolving the headers, so I think it's logical
> that -M (or "-fmodules-list-dependencies" or whatever...) could also
> respect where the prebuild dir is and spit out the PCM paths (or even
> better the original CPPMs' -- I think PCM contains a backwards link to
> where it was built from?) the TU depends on.
Yep, build integration with modules is still very much uncertain/unknown.
Experiments/ideas/prototypes are all being played with - but more
experiments/design suggestions are welcome.
GCC is prototyping a "callback" system of sorts - when the compiler needs a
BMI (binary module interface - Clang's are the .pcm files) it would
callback into the build system to ask for the file path of the BMI (so the
build system could go off and build it, then inform the compiler where it
Clang requires it all explicit at the moment, as I showed above - the build
system could either have its own import/inclusion discovery or maybe -M
could be expanded to support imports, etc.
> David Blaikie via cfe-dev <cfe-dev at lists.llvm.org> ezt írta (időpont:
> 2018. okt. 4., Cs, 20:02):
> > Yeah, Richard seems to be working on modules TS features when he has
> time amongst other priorities.
> > Any particular areas you've found gaps you've been interested in filling?
> > On Sat, Sep 29, 2018 at 8:15 AM Matt Asplund (mwasplund) via cfe-dev <
> cfe-dev at lists.llvm.org> wrote:
> >> Hello,
> >> I am curious if there is any active work being done on the Modules TS
> implementation. I would like to help fill in the gaps that I am finding
> while playing around with it and wanted to make sure I wasn’t duplicating
> >> -Matt
> >> _______________________________________________
> >> cfe-dev mailing list
> >> cfe-dev at lists.llvm.org
> >> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
> > _______________________________________________
> > cfe-dev mailing list
> > cfe-dev at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev