[cfe-dev] USR for CTU analysis

[Kihong Heo via cfe-dev]

Hi Gabor,

Thanks for your answer.
But this is a C program. What does template mean in C?

Also, ASTImporter sometimes raises “name conflict” even though the function has a unique name and the AST file is in ctu-dir.
When does “name conflict” happen?

Kihong


> On May 20, 2019, at 8:38 AM, Gábor Márton <martongabesz at gmail.com> wrote:
> 
> Taking a look at USRGeneration.cpp, it seems to me that '#l#l' indicates two (template?) arguments with ulong types.
> 
> Gabor
> 
> On Sat, May 18, 2019 at 10:43 PM Kihong Heo via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote:
> Hi list,
> 
> index::generateUSRForDecl sometimes returns USR names followed by special characters such as
> 
> c:@F at UA_memoryManager_calloc#l#l
> c:ua_types.c at F@clear_noInit#*v#*1$@S at UA_DataType#
> 
> Could someone explain what “#l#l” mean?
> And the second case looks quite different from other cases. It would be appreciated if you could give some explanation.
> 
> Thanks,
> Kihong
> 
> 
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev <https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20190520/56e306d7/attachment.html>