And add tests: when both --prefix(-B) and --gcc-toolchain are specified, the GCC
installation with the largest version wins. This just documents the
current behavior.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
This is motivated by Linux kernel folks' confusion on --gcc-toolchain https://lore.kernel.org/linux-kbuild/20210303230708.l6pbk5o5nc2qa5of@google.com/
(it confused me, even if I had stared at this piece code a few times before!)
The command line option documentation is currently a bit messy, and lacks much information.
We probably need something similar to include/clang/Basic/AttrDocs.td by @aaron.ballman
I choose to add it inline before the infrastructure is available.
I understand --gcc-toolchain as a replacement for configure-time replacement for GCC_INSTALL_PREFIX. This option probably should not have existed:(
clang/docs/ClangCommandLineReference.rst | ||
---|---|---|
23 | I like how --gcc-toolchain references -B; can -B also reference --gcc-toolchain? That way developers also understand their options when looking at either? Or should we move --gcc-toolchain to be closer to -B, since they're slightly similar? | |
259 | Add whitespace after periods. | |
clang/include/clang/Driver/Options.td | ||
603 | s/includes/includes,/ |
comments
clang/docs/ClangCommandLineReference.rst | ||
---|---|---|
23 | clang-tblgen -I ../llvm/include -I include/clang/Driver -gen-opt-docs include/clang/Driver/ClangOptionDocs.td sorts the options alphabetically so it is not easy to move them together... |
I like how --gcc-toolchain references -B; can -B also reference --gcc-toolchain? That way developers also understand their options when looking at either? Or should we move --gcc-toolchain to be closer to -B, since they're slightly similar?