public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cel at us dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29814] [gdb/tdep, powerpc64le] FAIL: gdb.base/msym-bp-shl.exp: debug=0: before run: info breakpoint
Date: Wed, 23 Nov 2022 16:37:10 +0000 [thread overview]
Message-ID: <bug-29814-4717-2r8zqlgkL6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29814-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29814
--- Comment #6 from Carl E Love <cel at us dot ibm.com> ---
FYI
I do not see the failure on Power 10, gcc (GCC) 12.2.1 20220819 (Red Hat
12.2.1-2), Fedora release 36 (Thirty Six). With mainline gdb
commit 31c1130f35e0ef800ea4d92224a72872ffe4a5db (HEAD -> master, origin/master,
origin/HEAD)
Author: GDB Administrator <gdbadmin@sourceware.org>
Date: Tue Nov 22 00:00:39 2022 +0000
Automatic date update in version.in
I do not see the failure on Power 10, gcc (GCC) 11.2.1 20220127 (Red Hat
11.2.1-9), Red Hat Enterprise Linux release 9.0 (Plow), with mainline gdb
commit 8db533e7d6d28db1be0ae4c95ddea7aa3a6224c8 (HEAD -> master, origin/master,
origin/HEAD)
Author: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
Date: Wed Nov 23 11:58:31 2022 +0100
gdb/arm: Include FType bit in EXC_RETURN pattern on v8m
The failure does occur on Power 9, gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1)
9.4.0,NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" with mainline gdb
commit 8db533e7d6d28db1be0ae4c95ddea7aa3a6224c8 (HEAD -> master, origin/master,
origin/HEAD)
Author: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
Date: Wed Nov 23 11:58:31 2022 +0100
gdb/arm: Include FType bit in EXC_RETURN pattern on v8m
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-23 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 13:27 [Bug tdep/29814] New: " vries at gcc dot gnu.org
2022-11-21 16:32 ` [Bug tdep/29814] " vries at gcc dot gnu.org
2022-11-23 10:14 ` vries at gcc dot gnu.org
2022-11-23 11:11 ` vries at gcc dot gnu.org
2022-11-23 11:59 ` uweigand at gcc dot gnu.org
2022-11-23 16:16 ` vries at gcc dot gnu.org
2022-11-23 16:37 ` cel at us dot ibm.com [this message]
2022-11-23 17:03 ` uweigand at gcc dot gnu.org
2022-11-23 20:43 ` cel at us dot ibm.com
2022-11-24 12:45 ` vries at gcc dot gnu.org
2022-11-28 9:50 ` cvs-commit at gcc dot gnu.org
2022-11-28 9:51 ` vries at gcc dot gnu.org
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=bug-29814-4717-2r8zqlgkL6@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).