libitm: Disable diagnostic coloring in tests
authorNathan Sidwell <nathan@acm.org>
Tue, 5 May 2020 19:50:54 +0000 (12:50 -0700)
committerNathan Sidwell <nathan@acm.org>
Tue, 5 May 2020 19:50:54 +0000 (12:50 -0700)
Diagnostic coloring makes the log file hard to read when there's a
problem.  Let's do without it.

            * Testsuite/lib/libitm.exp (libitm_init): Add
            -fdiagnostics-color=never to options.

libitm/ChangeLog
libitm/testsuite/lib/libitm.exp

index 9c70974776cfce89ed4e6de9b02ca776dc9c79d2..37a1b443e11c80bb7bf4c97639ff3dae4e83779c 100644 (file)
@@ -1,3 +1,8 @@
+2020-05-05  Nathan Sidwell  <nathan@acm.org>
+
+       * testsuite/lib/libitm.exp (libitm_init): Add
+       -fdiagnostics-color=never to options.
+
 2020-02-12  Sandra Loosemore  <sandra@codesourcery.com>
 
        PR libstdc++/79193
index b3d247b9f98a1fce8651726910f8fe13a49b23d9..6d8e3e71310c945a931465d91425b33a57ea8332 100644 (file)
@@ -175,6 +175,8 @@ proc libitm_init { args } {
 
     # Turn on transactional memory support.
     lappend ALWAYS_CFLAGS "additional_flags=-fgnu-tm"
+
+    lappend ALWAYS_CFLAGS "additional_flags=-fdiagnostics-color=never"
 }
 
 #