Also manages clang-X as tool for scan-build

[sylvestre.ledru]

Summary

This will make
scan-build-7 clang-7 -c foo.c &> /dev/null

[kristina]

Nitpick: This regex is far too broad to cover the rare use case where you'd be invoking clang as clang-N. I think something like clang(?:\-[789])? would be more suitable?

[jroelofs]

lgtm

[sylvestre.ledru]

@kristina sorry, I missed your comment. I just followed what we are doing with gcc. Do you want me to update it?

[kristina]

Just a minor suggestion, I think it would make it more clear as before LLVM 7, Clang did not have a version number with the main executable. GCC is slightly less consistent with their formats as they usually ship as host compilers with various suffixes, but with Clang it can only be clang, clang-7 or 8 (or 9 in the future) although it's still generally invoked as clang unless you have multiple installations.

[jroelofs]

$triple-clang, also

tools/scan-build/bin/scan-build

sub RunBuildCommand {
   }
 
   # Setup the environment.
   SetEnv($EnvVars);
 
   if ($Cmd =~ /(.*\/?gcc[^\/]*$)/ or
       $Cmd =~ /(.*\/?cc[^\/]*$)/ or
       $Cmd =~ /(.*\/?llvm-gcc[^\/]*$)/ or
-      $Cmd =~ /(.*\/?clang$)/ or
+      $Cmd =~ /(.*\/?clang[^\/]*$)/ or
       $Cmd =~ /(.*\/?ccc-analyzer[^\/]*$)/) {
 
     if (!($Cmd =~ /ccc-analyzer/) and !defined $ENV{"CCC_CC"}) {
       $ENV{"CCC_CC"} = $1;
     }
 
     shift @$Args;
     unshift @$Args, $CCAnalyzer;