[PATCH] D109621: [clang] [Driver] Fall back to default.cfg when calling clang w/o prefix

mgorny abandoned this revision. mgorny added a comment. Abandoning in favor of D134337 . CHANGES SINCE LAST ACTION https://reviews.llvm.org/D109621/new/ https://reviews.llvm.org/D109621 ___ cfe-commits mailing

[PATCH] D109621: [clang] [Driver] Fall back to default.cfg when calling clang w/o prefix

mgorny added a comment. In D109621#3799133 , @sepavloff wrote: > In D109621#3791511 , @mstorsjo > wrote: > >> On this topic, it would be great if we could pick up a per-target default >> config file too, if

[PATCH] D109621: [clang] [Driver] Fall back to default.cfg when calling clang w/o prefix

sepavloff added a comment. In D109621#3791511 , @mstorsjo wrote: > On this topic, it would be great if we could pick up a per-target default > config file too, if clang is invoked with `clang -target `. Currently > this is done automatically if clang

[PATCH] D109621: [clang] [Driver] Fall back to default.cfg when calling clang w/o prefix

mgorny added inline comments. Comment at: clang/docs/UsersManual.rst:915 +in the directory where Clang resides. If Clang is started via an executable +without target prefix, Clang will use ``default.cfg`` instead. sepavloff wrote: > What about using default

[PATCH] D109621: [clang] [Driver] Fall back to default.cfg when calling clang w/o prefix

sepavloff added inline comments. Comment at: clang/docs/UsersManual.rst:915 +in the directory where Clang resides. If Clang is started via an executable +without target prefix, Clang will use ``default.cfg`` instead. What about using default config based on

[PATCH] D109621: [clang] [Driver] Fall back to default.cfg when calling clang w/o prefix

mgorny updated this revision to Diff 461054. mgorny added a comment. Fix documentation formatting. While at it, fix a doc mistake that referenced `x86_64-cl.cfg` instead of the correct `x86_64-clang-cl.cfg`. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D109621/new/

[PATCH] D109621: [clang] [Driver] Fall back to default.cfg when calling clang w/o prefix

mgorny added a comment. As an example, we are currently installing the following set of executables + symlinks for clang in Gentoo on amd64 with full multilib: lrwxrwxrwx 1 root root8 Sep 17 12:31 /usr/lib/llvm/16/bin/clang -> clang-16 lrwxrwxrwx 1 root root 10 Sep 17 12:31

[PATCH] D109621: [clang] [Driver] Fall back to default.cfg when calling clang w/o prefix

mgorny added inline comments. Comment at: clang/docs/UsersManual.rst:878 Another way to specify a configuration file is to encode it in executable name. For example, if the Clang executable is named `armv7l-clang` (it may be a +symbolic link to `clang`), then Clang will search

[PATCH] D109621: [clang] [Driver] Fall back to default.cfg when calling clang w/o prefix

mgorny updated this revision to Diff 460877. mgorny retitled this revision from "[clang][Driver] Default to loading clang.cfg if config file not specified" to "[clang] [Driver] Fall back to default.cfg when calling clang w/o prefix". mgorny edited the summary of this revision. mgorny added a