mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-06-22 11:00:01 +08:00
gdb/fortran: test case modified to suit the clang behavior.
As mentioned in the test case itself, depending on the fortran compiler used, class member names used in the print commands and also output of these print commands varies. Existing print commands and its output are suited for gfortran, hence they were failing with clang compiler and test case was modified accordingly for clang compiler. gdb/testsuite/ChangeLog: * gdb.base/class-allocatable-array.exp: Modified test for clang.
This commit is contained in:

committed by
Alok Kumar Sharma

parent
f4fdd84587
commit
467f8eb233
@ -1,3 +1,7 @@
|
||||
2021-05-17 Bhuvanendra Kumar N <Bhuvanendra.KumarN@amd.com>
|
||||
|
||||
* gdb.base/class-allocatable-array.exp: Modified test for clang.
|
||||
|
||||
2021-05-16 Weimin Pan <weimin.pan@oracle.com>
|
||||
|
||||
* gdb.ctf/funcreturn.exp: New file.
|
||||
|
@ -38,6 +38,13 @@ gdb_continue_to_breakpoint "Break Here"
|
||||
# different names, or maybe a completely different approach, for
|
||||
# representing class like structures. The following tests are
|
||||
# cetainly going to fail.
|
||||
gdb_test "print this" " = \\( _data = \[^\r\n\]+, _vptr = \[^\r\n\]+\\)"
|
||||
gdb_test "print this%_data" " = \\(PTR TO -> \\( Type test_type \\)\\) \[^\r\n\]+"
|
||||
gdb_test "print this%_data%b" " = \\(\\(1, 2, 3\\) \\(4, 5, 6\\)\\)"
|
||||
# Hence the test case is modified for clang.
|
||||
if {[test_compiler_info {clang-*}]} {
|
||||
gdb_test "print this" " = \\( a = 0, b = \\(\\(1, 2, 3\\) \\(4, 5, 6\\)\\) \\)"
|
||||
gdb_test "print this%a" " = 0"
|
||||
gdb_test "print this%b" " = \\(\\(1, 2, 3\\) \\(4, 5, 6\\)\\)"
|
||||
} else {
|
||||
gdb_test "print this" " = \\( _data = \[^\r\n\]+, _vptr = \[^\r\n\]+\\)"
|
||||
gdb_test "print this%_data" " = \\(PTR TO -> \\( Type test_type \\)\\) \[^\r\n\]+"
|
||||
gdb_test "print this%_data%b" " = \\(\\(1, 2, 3\\) \\(4, 5, 6\\)\\)"
|
||||
}
|
||||
|
Reference in New Issue
Block a user