* If ccache guesses that the compiler may emit colored warnings, then a
compilation with stderr referring to a TTY will be considered different from
a compilation with a redirected stderr, thus not sharing cache entries. This
- happens for clang by default and for GCC when *GCC_COLORS* is set as
+ happens for Clang by default and for GCC when *GCC_COLORS* is set as
mentioned above. If you want to share cache hits, you can pass
- `-f[no-]diagnostics-color` (GCC) or `-f[no-]color-diagnostics` (clang)
+ `-f[no-]diagnostics-color` (GCC) or `-f[no-]color-diagnostics` (Clang)
explicitly when compiling (but then color codes will be either on or off for
both the TTY and the redirected case).
// The path to the stack usage (implicit when using -fstack-usage).
std::string output_su;
- // Diagnostic generation information (clang). Contains pathname if not empty.
+ // Diagnostic generation information (Clang). Contains pathname if not empty.
std::string output_dia;
// Split dwarf information (GCC 4.8 and up). Contains pathname if not empty.
bool profile_generate = false;
// Whether we are using a precompiled header (either via -include, #include or
- // clang's -include-pch or -include-pth).
+ // Clang's -include-pch or -include-pth).
bool using_precompiled_header = false;
// Files referenced by -fsanitize-blacklist options.
};
static const struct compopt compopts[] = {
- {"--analyze", TOO_HARD}, // clang
+ {"--analyze", TOO_HARD}, // Clang
{"--compiler-bindir", AFFECTS_CPP | TAKES_ARG}, // nvcc
{"--libdevice-directory", AFFECTS_CPP | TAKES_ARG}, // nvcc
{"--output-directory", AFFECTS_CPP | TAKES_ARG}, // nvcc
{"-Xlinker", TAKES_ARG | TAKES_CONCAT_ARG | AFFECTS_COMP},
{"-Xpreprocessor", AFFECTS_CPP | TOO_HARD_DIRECT | TAKES_ARG},
{"-all_load", AFFECTS_COMP},
- {"-analyze", TOO_HARD}, // clang
+ {"-analyze", TOO_HARD}, // Clang
{"-arch", TAKES_ARG},
{"-aux-info", TAKES_ARG},
{"-b", TAKES_ARG},
{"-fno-working-directory", AFFECTS_CPP},
{"-fplugin=libcc1plugin", TOO_HARD}, // interaction with GDB
{"-frepo", TOO_HARD},
- {"-ftime-trace", TOO_HARD}, // clang
+ {"-ftime-trace", TOO_HARD}, // Clang
{"-fworking-directory", AFFECTS_CPP},
{"-gtoggle", TOO_HARD},
{"-idirafter", AFFECTS_CPP | TAKES_ARG | TAKES_CONCAT_ARG | TAKES_PATH},
// as of 3.9 (see https://bugs.llvm.org/show_bug.cgi?id=25510). But if libgcc
// is used we have the same problem as mentioned above. Unfortunately there
// doesn't seem to be a way to detect which one is used, or the version of
-// libgcc when used by clang, so assume that it works with Clang >= 3.9.
+// libgcc when used by Clang, so assume that it works with Clang >= 3.9.
#if !(__GNUC__ >= 8 || (__GNUC__ == 7 && __GNUC_MINOR__ >= 4) \
|| (__GNUC__ == 6 && __GNUC_MINOR__ >= 5) || __clang_major__ > 3 \
|| (__clang_major__ == 3 && __clang_minor__ >= 9))