[llvm-dev] Implications of Module SourceFileName

[Adrian McCarthy via llvm-dev]

 Module is one of those overloaded terms that means different things in
different contexts.  I'm not sure how module file names are propagated into
the debug info.  You might want to check in with the lldb folks, too, to
see if a list of file names like that will hinder the debugger.

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/47b9ec81/attachment.html>