[llvm-dev] Implications of Module SourceFileName (original) (raw)

David Blaikie via llvm-dev llvm-dev at lists.llvm.org
Tue May 26 11:41:58 PDT 2020

Does your source language's concept of Module have to/have any bearing on the llvm concept of a Module? (ie: do all the source files need to be compiled in one go/together into one file? C++'s concept of a module doesn't have this, for instance... I /think/ at least that each fragment of a module can be compiled separately - which is good for build parallelism, etc)

On Mon, May 25, 2020 at 3:23 PM Rarrum via llvm-dev <llvm-dev at lists.llvm.org> wrote:

In the language I'm working on, a module (which does have a user-defined name in source) may be comprised of several files. I'm considering passing the (user-defined) name to llvm::Module's setModuleIdentifier, then a semicolon separated list of file names to setSourceFileName. Is this going to cause unforeseen problems?

https://releases.llvm.org/10.0.0/docs/LangRef.html#source-filename seems to imply that it only needs to be a "consistent unique global identifier", but then also shows a unix-style path as the syntax. I don't see anything crazy being done with it from a quick source of llvm's source.

LLVM Developers mailing list llvm-dev at lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200526/a8ce3108/attachment.html>

More information about the llvm-dev mailing list