diff options
| author | Tom de Vries <tdevries@suse.de> | 2024-06-07 08:12:34 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2024-06-07 08:12:34 +0200 |
| commit | f9478936896ada7786e8d68622f6e6ff78b97b0d (patch) | |
| tree | 357762ea15c9f78476b74dcb0adc3164565e59a9 /gdb/ui-file.c | |
| parent | a5631e3da1d9574aa0094f87efd8785ba16a0df7 (diff) | |
| download | gdb-f9478936896ada7786e8d68622f6e6ff78b97b0d.zip gdb-f9478936896ada7786e8d68622f6e6ff78b97b0d.tar.gz gdb-f9478936896ada7786e8d68622f6e6ff78b97b0d.tar.bz2 | |
[gdb/testsuite] Fix gdb.fortran/array-bounds.exp on arm
When running test-case gdb.fortran/array-bounds.exp on arm-linux, we run into:
...
(gdb) print &foo^M
$1 = (PTR TO -> ( real(kind=4) (0:1) )) 0xfffef008^M
(gdb) FAIL: gdb.fortran/array-bounds.exp: print &foo
print &bar^M
$2 = (PTR TO -> ( real(kind=4) (-1:0) )) 0xfffef010^M
(gdb) FAIL: gdb.fortran/array-bounds.exp: print &bar
...
This is due to gcc PR debug/54934.
The test-case contains a kfail for this, which is only activated for
x86_64/i386.
Fix this by enabling the kfail for all ilp32 targets.
Also:
- change the kfail into an xfail, because gdb is not at fault here, and
- limit the xfail to the gfortran compiler.
Tested on arm-linux.
Diffstat (limited to 'gdb/ui-file.c')
0 files changed, 0 insertions, 0 deletions