Blame SOURCES/gcc11-dejagnu-multiline.patch

f49307
commit 14c7757e9b751781360737f53b71f851fc356d3d
f49307
Author: Jeff Law <jeffreyalaw@gmail.com>
f49307
Date:   Fri Oct 29 11:30:15 2021 -0400
f49307
f49307
    Avoid overly-greedy match in dejagnu regexp.
f49307
    
f49307
    Occasionally I've been seeing failures with the multi-line diagnostics.  It's never been clear what's causing the spurious failures, though I have long suspected a greedy regexp match.
f49307
    
f49307
    It happened again yesterday with a local change that in no way should affect diagnostics, so I finally went searching and found that sure enough the multi-line diagnostics had a ".*" in their regexp.  According to the comments, the .* is primarily to catch any dg directives that may appear -- ie it should eat to EOL, but not multiple lines.  But a .* can indeed match a newline and cause it to eat multiple lines.
f49307
    
f49307
    The fix is simple.  [^\r\n]* will eat to EOL, but not further.
f49307
    
f49307
    Regression tested on x86_64 and on our internal target.
f49307
    
f49307
    gcc/testsuite
f49307
    
f49307
            * lib/multiline.exp (_build_multiline_regex): Use a better
f49307
            regexp than .* to match up to EOL.
f49307
f49307
diff --git a/gcc/testsuite/lib/multiline.exp b/gcc/testsuite/lib/multiline.exp
f49307
index 0e151b6d222..86387f8209b 100644
f49307
--- a/gcc/testsuite/lib/multiline.exp
f49307
+++ b/gcc/testsuite/lib/multiline.exp
f49307
@@ -331,7 +331,7 @@ proc _build_multiline_regex { multiline index } {
f49307
 		# Support arbitrary followup text on each non-empty line,
f49307
 		# to deal with comments containing containing DejaGnu
f49307
 		# directives.
f49307
-		append rexp ".*"
f49307
+		append rexp "\[^\\n\\r\]*"
f49307
 	    }
f49307
 	}
f49307
 	append rexp "\n"