[clang] [clang] Diagnose config_macros before building modules (PR #83641)

[Volodymyr Sapsai via cfe-commits]

================
@@ -22,7 +58,10 @@
 #define WANT_BAR 1 // expected-note{{macro was defined here}}
 @import config; // expected-warning{{definition of configuration macro 'WANT_BAR' has no effect on the import of 'config'; pass '-DWANT_BAR=...' on the command line to configure the module}}
 
-// RUN: rm -rf %t
-// RUN: %clang_cc1 -std=c99 -fmodules -fimplicit-module-maps -x objective-c -fmodules-cache-path=%t -DWANT_FOO=1 -emit-module -fmodule-name=config %S/Inputs/module.modulemap
-// RUN: %clang_cc1 -std=c99 -fmodules -fimplicit-module-maps -fmodules-cache-path=%t -I %S/Inputs -DWANT_FOO=1 %s -verify
+//--- config_error.m
----------------
vsapsai wrote:

That works. I like how for other cases we have the *intention* of the test written down. And I don't think it would lead to the proliferation of "config_error2.m", "config_error3.m".

https://github.com/llvm/llvm-project/pull/83641