From b9735db6464cf0bb4f60077b9f5495c0fa372ecf Mon Sep 17 00:00:00 2001
From: "Joel E. Denny" <jdenny.ornl@gmail.com>
Date: Wed, 21 Sep 2022 13:27:41 -0400
Subject: [PATCH] [lit] Work around windows issue in new test from 28412d1800e3

Based on result shown at:

<https://lab.llvm.org/buildbot/#/builders/216/builds/10120>
---
 .../utils/lit/tests/Inputs/shtest-define/value-escaped.txt | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/llvm/utils/lit/tests/Inputs/shtest-define/value-escaped.txt b/llvm/utils/lit/tests/Inputs/shtest-define/value-escaped.txt
index 844d53ebc54e..58d5c1a34ce8 100644
--- a/llvm/utils/lit/tests/Inputs/shtest-define/value-escaped.txt
+++ b/llvm/utils/lit/tests/Inputs/shtest-define/value-escaped.txt
@@ -1,13 +1,16 @@
+# FIXME: The doubled backslashes occur under windows.  That's almost surely a
+# lit issue beyond DEFINE/REDEFINE.
+
 # Escape sequences that can appear in python re.sub replacement strings have no
 # special meaning in the value.
 
 # DEFINE: %{escape} = \g<0>\n
 # RUN: echo '%{escape}'
-# CHECK: \g<0>\n
+# CHECK: {{\\?}}\g<0>{{\\?}}\n
 
 # REDEFINE: %{escape} = \n                                                     \
 # REDEFINE:             \g<param>
 # RUN: echo '%{escape}'
-# CHECK: \n \g<param>
+# CHECK: {{\\?}}\n {{\\?}}\g<param>
 
 # CHECK: Passed: 1