ChuanqiXu added a comment. @sammccall here is a question (or double check) about the intended initial version.
This is the requirement for the initial version: > Don't attempt any cross-file or cross-version coordination: i.e. don't try to > reuse BMIs between different files, don't try to reuse BMIs between > (preamble) reparses of the same file, don't try to persist the module graph. > Instead, when building a preamble, synchronously scan for the module graph, > build the required PCMs on the single preamble thread with filenames private > to that preamble, and then proceed to build the preamble. And all of us agree that it will be the job of the preamble to manage the module files in the end of the day. I just want to ask or double check that it might be OK to not related the module files with preamble in the initial version, right? Since the definition (or description) of preamble is: > A preamble can be reused between multiple versions of the file until > invalidated by a modification to a header, compile commands or modification > to relevant part of the current file. And it looks like it beyonds the scope of the our requirement of the initial patch. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D153114/new/ https://reviews.llvm.org/D153114 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
