<div dir="ltr">Hi Joel,<div><br></div><div></div><div>clangd, clang-tidy and other tools do not require to be built from the same revision as the host compiler that the project uses to build code. In fact, the compiler is not necessarily clang, it can be gcc or MSVC.</div><div>However, the internal clang headers (the ones -resource-dir points at) must correspond to the same version of the code that the clang frontend is built from. <br></div><div>So the aforementioned tools ship their own version of clang's internal headers and pass -resource-dir to the clang frontend to make sure the frontend picks them up. I.e. if the host compiler is also clang, the tools <b>must not </b>pick the host clang's internal headers.</div><div><div>The tools take other compilation arguments from a compilation database (compile_commands.json).</div><div></div></div><div><br></div><div>Note that the internal headers is the only thing that the tools need to override, e.g. this should not affect the C++ standard library found by the tools.</div><div>For that to work, we have to make sure the internal headers is the only thing affected by "-resource-dir", we don't want the tools to see a different standard library (or not find a standard library at all).</div><div><br></div><div>So far in cases where -resource-dir was used for finding libc++, replacing it with "compiler install dir" ("Driver.InstalledDir") seemed to do the job.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 27, 2019 at 12:09 AM Joel E. Denny <<a href="mailto:jdenny.ornl@gmail.com" target="_blank">jdenny.ornl@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Ilya,<br>
<br>
On Mon, Feb 25, 2019 at 5:32 AM Ilya Biryukov <<a href="mailto:ibiryukov@google.com" target="_blank">ibiryukov@google.com</a>> wrote:<br>
><br>
> > From this point of view, what LLVM_ENABLE_PER_TARGET_RUNTIME_DIR breaks the tools and the proposed alternative fixes this problem<br>
> what LLVM_ENABLE_PER_TARGET_RUNTIME_DIR does now ...<br>
><br>
> On Mon, Feb 25, 2019 at 11:31 AM Ilya Biryukov <<a href="mailto:ibiryukov@google.com" target="_blank">ibiryukov@google.com</a>> wrote:<br>
>><br>
>> Using the resource-dir in the header search paths would break tools that use compilation database, e.g. clang-tidy and clangd.<br>
>> They override the resource-dir as it's very common for them to be built from a different revision than the used compiler. They rely on the fact that the same standard library can be found with the overridden resouce-dir.<br>
>><br>
>> From this point of view, what LLVM_ENABLE_PER_TARGET_RUNTIME_DIR breaks the tools and the proposed alternative fixes this problem.<br>
<br>
Thanks for pointing this out. I'd like to better understand, but I'm<br>
only familiar with clang-tidy and clangd from a high level. Can you<br>
explain a bit more about how they interact with the used compiler and<br>
how they use the overridden resource directory?<br>
<br>
Thanks.<br>
<br>
Joel<br>
<br>
>><br>
>> On Mon, Feb 25, 2019 at 11:17 AM Petr Hosek via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br>
>>><br>
>>> On Wed, Feb 20, 2019 at 6:14 PM Joel E. Denny <<a href="mailto:jdenny.ornl@gmail.com" target="_blank">jdenny.ornl@gmail.com</a>> wrote:<br>
>>>><br>
>>>> My alternative to LLVM_ENABLE_PER_TARGET_RUNTIME_DIR is the preceding<br>
>>>> bullets. In other words, you wouldn't need to specify<br>
>>>> LLVM_ENABLE_PER_TARGET_RUNTIME_DIR because it would effectively be<br>
>>>> always on (except the directories might be different than now if the<br>
>>>> version locking issue is important, as noted above). Is that what<br>
>>>> you're asking?<br>
>>><br>
>>><br>
>>> That would be my preference. I always hoped that LLVM_ENABLE_PER_TARGET_RUNTIME_DIR would eventually become the default. It would be nice to finish the Darwin support so we can completely deprecate the old layout, but I don't know how far along beanz is in his effort. We should also update openmp to stop using the custom Android-specific runtime layout.<br>
>>><br>
>>> There's also the unresolved question of where should libc++ headers and libraries go. Currently, in LLVM_ENABLE_PER_TARGET_RUNTIME_DIR we use the resource dir, but some people expressed the opinion that we shouldn't be using these for libc++ et al. since they're not version-locked to Clang. This is different from what GCC does (e.g. GCC would use $prefix/lib/gcc/x86_64-linux-gnu/8/libstdc++.a) and it's one of the reasons why I used the resource dir for libc++ et al. when implementing LLVM_ENABLE_PER_TARGET_RUNTIME_DIR.<br>
>>><br>
>>> So concretely, today LLVM_ENABLE_PER_TARGET_RUNTIME_DIR uses the following layout:<br>
>>><br>
>>> headers: $prefix/lib/clang/$version/include(/$triple)(/c++/v1)<br>
>>> libraries: $prefix/lib/clang/$version/$triple/lib/$name.$ext<br>
>>><br>
>>> The alternative that doesn't use resource dir for libc++ would be the following:<br>
>>><br>
>>> compiler-rt:<br>
>>> headers: $prefix/lib/clang/$version/include<br>
>>> libraries: $prefix/lib/clang/$version/$triple/lib/$name.$ext<br>
>>><br>
>>> libc++, libc++abi, libunwind:<br>
>>> headers: $prefix/include/c++/v1<br>
>>> libraries: $prefix/lib/$triple/$name.$ext<br>
>>><br>
>>> Making this change should be trivial, it's the matter of changing three CMakeLists.txt files (libunwind, libc++abi and libc++) and Clang driver in one place. However, if we're going to make that change, I'd like to get a broader consensus. It'd be also useful to get feedback from libc++ maintainers on this.<br>
>>> _______________________________________________<br>
>>> cfe-dev mailing list<br>
>>> <a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
>>> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
>><br>
>><br>
>><br>
>> --<br>
>> Regards,<br>
>> Ilya Biryukov<br>
><br>
><br>
><br>
> --<br>
> Regards,<br>
> Ilya Biryukov<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_1788601489473298431gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Regards,</div><div>Ilya Biryukov</div></div></div></div></div>