diff options
| author | Tom de Vries <tdevries@suse.de> | 2020-08-05 12:31:58 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2020-08-05 12:31:58 +0200 |
| commit | 5555c86d3e85e85d76555acdb955aba062beb02f (patch) | |
| tree | f143fead64487d5b67f196ba939c9934a77651a4 /gdb/testsuite/gdb.dwarf2/valop.S | |
| parent | 787bbc56d895b452ebfe90bc2b1345ca825fa412 (diff) | |
| download | gdb-5555c86d3e85e85d76555acdb955aba062beb02f.zip gdb-5555c86d3e85e85d76555acdb955aba062beb02f.tar.gz gdb-5555c86d3e85e85d76555acdb955aba062beb02f.tar.bz2 | |
[gdb] Fix prop->const_val uses in gdbtypes.c
After commit 66d6346b25 "gdb: remove TYPE_DYN_PROP_ADDR", I run into:
...
FAIL: gdb.fortran/class-allocatable-array.exp: print this%_data%b
...
(and 185 more FAILs, all for fortran test-cases).
The commit replaces "!x" by "x != 0".
Fix this by using "x == 0" instead.
Build and tested on x86_64-linux.
gdb/ChangeLog:
2020-08-05 Tom de Vries <tdevries@suse.de>
* gdbtypes.c (type_not_allocated, type_not_associated): Use
"prop->const_val () == 0" instead of "prop->const_val () != 0".
Diffstat (limited to 'gdb/testsuite/gdb.dwarf2/valop.S')
0 files changed, 0 insertions, 0 deletions