public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/29432] [gdb, tdep/s390x/ppc64] Self test failed: self-test failed at arm-tdep.c:14482 (selftest arm-record) Date: Sat, 30 Jul 2022 11:29:26 +0000 [thread overview] Message-ID: <bug-29432-4717-6mlbnm2zqa@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29432-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29432 Mark Wielaard <mark at klomp dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[gdb, tdep/s390x] Self test |[gdb, tdep/s390x/ppc64] |failed: self-test failed at |Self test failed: self-test |arm-tdep.c:14482 (selftest |failed at arm-tdep.c:14482 |arm-record) |(selftest arm-record) --- Comment #2 from Mark Wielaard <mark at klomp dot org> --- Same test fails on ppc64 (big endian) Also see https://sourceware.org/pipermail/gdb/2022-July/050215.html and https://sourceware.org/pipermail/gdb/2022-July/050217.html -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-30 11:29 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-30 8:08 [Bug tdep/29432] New: [gdb, tdep/s390x] " vries at gcc dot gnu.org 2022-07-30 8:08 ` [Bug tdep/29432] " vries at gcc dot gnu.org 2022-07-30 9:26 ` vries at gcc dot gnu.org 2022-07-30 11:29 ` mark at klomp dot org [this message] 2022-08-03 11:56 ` [Bug tdep/29432] [gdb, tdep/s390x/ppc64] " mark at klomp dot org 2022-08-03 11:58 ` luis.machado at arm dot com 2022-08-03 11:58 ` luis.machado at arm dot com 2022-08-08 10:16 ` luis.machado at arm dot com 2022-09-07 17:25 ` 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-29432-4717-6mlbnm2zqa@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: linkBe 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).