From: Abhay Kandpal <abhay@linux.ibm.com>
To: aburgess@redhat.com
Cc: gdb-patches@sourceware.org, Ulrich.Weigand@de.ibm.com, cel@linux.ibm.com
Subject: PPC64LE: New failures in empty-inline-cxx.exp after commit 196349e7e5939c2
Date: Tue, 10 Feb 2026 10:42:10 +0530 [thread overview]
Message-ID: <7fd2cc58-33ab-420a-83ba-e98cae69b028@linux.ibm.com> (raw)
In-Reply-To: <20260205093747.-PO3F%cel@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]
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 <mailto: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
[-- Attachment #2: Type: text/html, Size: 3583 bytes --]
next parent reply other threads:[~2026-02-10 5:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260205093747.-PO3F%cel@linux.ibm.com>
2026-02-10 5:12 ` Abhay Kandpal [this message]
2026-02-11 9:58 ` Andrew Burgess
2026-02-11 10:39 ` Andrew Burgess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fd2cc58-33ab-420a-83ba-e98cae69b028@linux.ibm.com \
--to=abhay@linux.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=aburgess@redhat.com \
--cc=cel@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox