[PATCH] D134337: [clang] [Driver] More flexible rules for loading default configs

Tue Oct 18 08:55:07 PDT 2022

tstellar added a comment.

In D134337#3864288 <https://reviews.llvm.org/D134337#3864288>, @mgorny wrote:

> In D134337#3863744 <https://reviews.llvm.org/D134337#3863744>, @tstellar wrote:
>
>> In what scenarios will clang load the clang.cfg file?
>
> It will load it if all of the following are true:
>
> 1. `--no-default-config` is **not** passed.
> 2. a more specific `<triple>-clang.cfg` is not found.
> 3. `--driver-mode=gcc` is in effect **or** the executable is named `clang` or `*-clang` and `--driver-mode=` did not select another config file.

I know I'm a little late here, but having a default config file that's always loaded makes triaging issues much harder, because now every time someone files a bug, we need to ask for the contents of their config directory.

================
Comment at: clang/docs/UsersManual.rst:954
+
+For example, ``x86_64-pc-linux-gnu-clang-g++`` will attempt to load two
+configuration files named respectively::
----------------
mgorny wrote:
> tstellar wrote:
> > Is `x86_64-pc-linux-gnu-clang-g++ ` being passed to --driver= in this example?
> I don't understand your question. `x86_64-pc-linux-gnu-clang-g++` is the executable (symlink) name here.
OK, it's a symlink.  That makes sense.

Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D134337