[gcc(refs/users/aoliva/heads/testme)] [testsuite] [vxworks] skip macros from implicitly-included vxConfig.h

[Alexandre Oliva via Gcc-cvs]

https://gcc.gnu.org/g:266afd9eea80fe2176be208980c3ff1f6403e57b

commit 266afd9eea80fe2176be208980c3ff1f6403e57b
Author: Alexandre Oliva <ol...@adacore.com>
Date:   Thu May 8 02:18:35 2025 -0300

    [testsuite] [vxworks] skip macros from implicitly-included vxConfig.h
    
    On vxworks, vxConfig.h is implicitly included, and it defines multiple
    macros in the namespace reserved for the implementation.
    
    g++.dg/modules/macro-5_a.H tests that macros from the command-line do
    not make the module output, but it can't tell them from macros from
    implicitly-included headers, so the test fails.
    
    Stricten the pattern to avoid matching reserved macro names.
    
    
    for  gcc/testsuite/ChangeLog
    
            * g++.dg/modules/macro-5_a.H: Don't match macros in the
            namespace reserved for the implementation.

Diff:
---
 gcc/testsuite/g++.dg/modules/macro-5_a.H | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/g++.dg/modules/macro-5_a.H 
b/gcc/testsuite/g++.dg/modules/macro-5_a.H
index d0913d1c53e5..a44a82abfae5 100644
--- a/gcc/testsuite/g++.dg/modules/macro-5_a.H
+++ b/gcc/testsuite/g++.dg/modules/macro-5_a.H
@@ -2,4 +2,4 @@
 // command line macros are not exported
 // { dg-module-cmi {} }
 
-// { dg-final { scan-lang-dump-not {Writing macro #define [_a-zA-Z0-9]* at 
[0-9]*} module } }
+// { dg-final { scan-lang-dump-not {Writing macro #define [a-z][_a-zA-Z0-9]* 
at [0-9]*} module } }