Hi Andrew,
We are seeing new test failures on our ppc64le systems after the upstream commit:
commit 196349e7e5939c2bef11fd93f098401d5b7111a5 (HEAD)
Author: Andrew Burgess <aburgess@redhat.com>
Date: Fri Sep 20 13:56:27 2024 +0100
gdb: handle empty ranges for inline subroutines
|
It appears that gdb.opt/empty-inline-cxx.exp was introduced as part of this change,
and this test is now failing consistently on ppc64le across all optimization levels. A sample failure is shown below:
gdb) run ^M
Starting program: /home/abhay/GDB/latest_gdb/build-gdb/gdb/testsuite/outputs/gdb.opt/empty-inline-cxx/empty-inline-cxx-Og ^M
[Thread debugging using libthread_db enabled]^M
Using host libthread_db library "/usr/lib64/libthread_db.so.1".^M
^M
Breakpoint 1, 0x0000000010000794 in main () at /home/abhay/GDB/latest_gdb/build-gdb/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.opt/empty-inline-cxx.cc:63^M
63 {^M
(gdb) bt^M
#0 0x0000000010000794 in main () at /home/abhay/GDB/latest_gdb/build-gdb/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.opt/empty-inline-cxx.cc:63^M
(gdb) FAIL: gdb.opt/empty-inline-cxx.exp: opt_level=Og: backtrace in main
break get_myclass^M
|
Summary of new failures:
+FAIL: gdb.opt/empty-inline-cxx.exp: opt_level=O0: backtrace in main
+FAIL: gdb.opt/empty-inline-cxx.exp: opt_level=O1: backtrace in main
+FAIL: gdb.opt/empty-inline-cxx.exp: opt_level=O2: backtrace in main
+FAIL: gdb.opt/empty-inline-cxx.exp: opt_level=Og: backtrace in main
|
Environment details:
OS: Fedora 43 (ppc64le)
Kernel: 6.17.6-300.fc43.ppc64le
GDB commit: 9b876c724da83d8ac8200afa3c87d873fc49ef16
Build/Install: OK
New failures: 4 (all in empty-inline-cxx.exp)
|
The test does not exist prior to this change.
This looks like a testsuite issue triggered by the new inline range handling on ppc64le.
Could you please take a look, or let me know if I need to update the test expectations for this target?
BR
Abhay Kandpal