diff options
author | Tom de Vries <tdevries@suse.de> | 2020-03-11 13:03:28 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2020-03-11 13:03:28 +0100 |
commit | 44f41bb7a1568dbe2e4e642e6c3c2e9ba3d47d92 (patch) | |
tree | d086e27e02eb95653649480d8e88867b382c9bae /gdb/testsuite/gdb.fortran/logical.f90 | |
parent | dcc050c86c3e5160497da7aab480adae9ba284aa (diff) | |
download | binutils-44f41bb7a1568dbe2e4e642e6c3c2e9ba3d47d92.zip binutils-44f41bb7a1568dbe2e4e642e6c3c2e9ba3d47d92.tar.gz binutils-44f41bb7a1568dbe2e4e642e6c3c2e9ba3d47d92.tar.bz2 |
[gdb/testsuite] Fix missing uint8_t in gdb.fortran/logical.exp
With test-case gdb.fortran/logical.exp, I run into:
...
(gdb) PASS: gdb.fortran/logical.exp: var=l: get hexadecimal valueof "&l"
set *((uint8_t *) 0x7fffffffd2bc) = 0xff^M
No symbol "uint8_t" in current context.^M
(gdb) FAIL: gdb.fortran/logical.exp: var=l: byte 0: set contents of byte at offset 0
...
Fix this by using the fortran-native type character instead.
Tested on x86_64-linux, with gcc 7.5.0.
gdb/testsuite/ChangeLog:
2020-03-11 Tom de Vries <tdevries@suse.de>
* gdb.fortran/logical.f90: Define variable with character type.
* gdb.fortran/logical.exp: Use character type instead of uint8_t.
Diffstat (limited to 'gdb/testsuite/gdb.fortran/logical.f90')
-rw-r--r-- | gdb/testsuite/gdb.fortran/logical.f90 | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.fortran/logical.f90 b/gdb/testsuite/gdb.fortran/logical.f90 index aea78e7..175dfd1 100644 --- a/gdb/testsuite/gdb.fortran/logical.f90 +++ b/gdb/testsuite/gdb.fortran/logical.f90 @@ -21,10 +21,12 @@ program test logical (kind=2) :: l2 logical (kind=4) :: l4 logical (kind=8) :: l8 + character :: c l = .TRUE. l1 = .TRUE. l2 = .TRUE. l4 = .TRUE. l8 = .TRUE. l = .FALSE. ! stop-here + c = 'a' end |