[clang] [clang][scan-build] Treat --use-cc and --use-c++ as shell commands (PR #131932)

2025-03-18 Thread Florian Ragwitz via cfe-commits
https://github.com/rafl created https://github.com/llvm/llvm-project/pull/131932 So that things like --use-cc="ccache gcc" work. Fixes #26594. Also use the slightly simpler shellwords instead of quotewords. Cc-ing the Clang static analyzer maintainers @haoNoQ, @Xazax-hun, and @steakhal. >From

[clang] [clang][scan-build] Treat --use-cc and --use-c++ as shell commands (PR #131932)

2025-03-19 Thread Florian Ragwitz via cfe-commits
rafl wrote: Thanks for your feedback, Balázs! > When I looked at this patch and I had the impression that `CCC_CXX` is > basically what one should use as `CXX` or `CMAKE_CXX_COMPILER`, which is just > a path to a binary - without any arguments. The author of the original code this change is m

[clang] [clang][scan-build] Treat --use-cc and --use-c++ as shell commands (PR #131932)

2025-03-21 Thread Florian Ragwitz via cfe-commits
https://github.com/rafl updated https://github.com/llvm/llvm-project/pull/131932 >From 3bdcfbbb56e80c1724a6e46597d0141c118c68cc Mon Sep 17 00:00:00 2001 From: Florian Ragwitz Date: Tue, 18 Mar 2025 15:35:42 -0700 Subject: [PATCH 1/5] [clang][scan-build] Treat --use-cc and --use-c++ as shell com

[clang] [clang][scan-build] Treat --use-cc and --use-c++ as shell commands (PR #131932)

2025-03-21 Thread Florian Ragwitz via cfe-commits
rafl wrote: > I'd prefer option 2, because why else would we have a default compiler if > that wasn't used in some workflows. A warning could never hurt. `--use-cc`/`--use-c++`/`CCC_CC`/`CCC_CXX` are optional, so the default would still be used when those options are not specified, which might

[clang] [clang][scan-build] Treat --use-cc and --use-c++ as shell commands (PR #131932)

2025-03-20 Thread Florian Ragwitz via cfe-commits
rafl wrote: Thanks for having another look @balazs-benics-sonarsource. While we wait for a potential second opinion, I was curious about what you think of the current behaviour of silently defaulting to `$Default{CC,CXX}Compiler` if `CCC_{CC,CXX}` isn't executable and can't be resolved to an

[clang] [clang][scan-build] Treat --use-cc and --use-c++ as shell commands (PR #131932)

2025-03-24 Thread Florian Ragwitz via cfe-commits
@@ -51,63 +51,40 @@ sub silent_system { # Compiler command setup. ##===--===## -# Search in the PATH if the compiler exists -sub SearchInPath { -my $file = shift; -foreach my $dir (split (':', $ENV{PA

[clang] [clang][scan-build] Treat --use-cc and --use-c++ as shell commands (PR #131932)

2025-03-24 Thread Florian Ragwitz via cfe-commits
@@ -51,63 +51,40 @@ sub silent_system { # Compiler command setup. ##===--===## -# Search in the PATH if the compiler exists -sub SearchInPath { -my $file = shift; -foreach my $dir (split (':', $ENV{PA

[clang] [clang][scan-build] Treat --use-cc and --use-c++ as shell commands (PR #131932)

2025-04-05 Thread Florian Ragwitz via cfe-commits
https://github.com/rafl edited https://github.com/llvm/llvm-project/pull/131932 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits