[PATCH] D117445: [lit] Expose clang search_env string as a use_clang argument

Amir Ayupov via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Mon Jan 17 23:18:06 PST 2022


Amir abandoned this revision.
Amir added a comment.

In D117445#3249645 <https://reviews.llvm.org/D117445#3249645>, @thopre wrote:

> In D117445#3249325 <https://reviews.llvm.org/D117445#3249325>, @Amir wrote:
>
>> In D117445#3247857 <https://reviews.llvm.org/D117445#3247857>, @thopre wrote:
>>
>>> What's the reason for not using `CLANG` instead of `BOLT_CLANG_EXE`?
>>
>> I'm a bit worried about an interference with other project tests (ie when bolt and clang are enabled and tests for both are invoked). But I agree it's unlikely to be an issue in practice.
>
> That's precisely what I cannot understand: why would you want the two projects to use a different clang? Sorry if the answer is obvious, I'm not familiar with bolt.

Yes, indeed, setting the `CLANG` env variable is sufficient. Thank you again for asking the right question!


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D117445/new/

https://reviews.llvm.org/D117445



More information about the llvm-commits mailing list