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

[Arfrever Frehtes Taifersar Arahesis via Phabricator via cfe-commits]

Arfrever added a comment.

After reading this discussion, I need some clarification.

If there were the followining symlinks pointing to `clang`: `i386-pc-linux-gnu-clang`, `i486-pc-linux-gnu-clang`, `i586-pc-linux-gnu-clang`, `i686-pc-linux-gnu-clang`, `x86_64-pc-linux-gnu-clang`.
Then do I assume correctly that:

1. `x86_64-pc-linux-gnu-clang -m32` would try to load `i386.cfg`
2. `i386-pc-linux-gnu-clang` would try to load `i386.cfg`
3. `i486-pc-linux-gnu-clang` would try to load `i486.cfg`
4. `i586-pc-linux-gnu-clang` would try to load `i586.cfg`
5. `i686-pc-linux-gnu-clang` would try to load `i686.cfg`

?

In modern multilib `x86_64` systems, only `i686-pc-linux-gnu-clang` and `x86_64-pc-linux-gnu-clang` symlinks (from above list) are likely to exist, but discrepancy in behavior between `x86_64-pc-linux-gnu-clang -m32` and `i686-pc-linux-gnu-clang` will cause confusion of users...


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D134337