OpenE2K/binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix array_char_idx.exp

Browse Source 
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.
This commit is contained in:
Tom Tromey 2020-05-15 10:25:56 -06:00
parent 250106a76a
commit b4757f2e45
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,7 @@
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

4
gdb/testsuite/gdb.ada/array_char_idx.exp
View File

@ -31,5 +31,7 @@ gdb_test "ptype char_table" \
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"