Newer versions of GCC can statically initialize an array in the
array_char_idx.exp test case. This leads to a spurious failure. This
patch fixes the problem by having the test case recognize both
possible results.
I'm checking this in.
gdb/testsuite/ChangeLog
2020-05-20 Tom Tromey <tromey@adacore.com>
* gdb.ada/array_char_idx.exp: Recognize initialized array.
+2020-05-20 Tom Tromey <tromey@adacore.com>
+
+ * gdb.ada/array_char_idx.exp: Recognize initialized array.
+
2020-05-20 Tom de Vries <tdevries@suse.de>
PR symtab/25833
gdb_test "ptype global_char_table" \
"= array \\(character\\) of natural"
-gdb_test "print my_table" "= \\(0 <repeats 256 times>\\)" \
+# Some more recent versions of gcc can statically initialize this
+# array, so we allow either 0 or 4874.
+gdb_test "print my_table" "= \\((0|4874) <repeats 256 times>\\)" \
"Display my_table"