Meinersbur wrote: > Another solution could be to extend the module file representation to hold > the several versions in the same module file (or at least the differences, > which would avoid artificially inflating the build size when building for > many targets). This assumes the host and device compilations are "atomic" > within the rest of the build, that is that no other compilation would start > using the host module before it is updated with the target info (so that the > hash of the new module file is stable).
That's what I meant with "multi-sections". In that case the driver would tell the frontend to emit the modules in some other place, and after all the targets have been processed, the driver combines all the modules into multi-section modules and writes them to the final `-module-dir` location. https://github.com/llvm/llvm-project/pull/200863 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
