public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "branislav.brzak at syrmia dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30571] New: [gdb, riscv] Ensure instructions are always fetches as LE Date: Wed, 21 Jun 2023 08:54:33 +0000 [thread overview] Message-ID: <bug-30571-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30571 Bug ID: 30571 Summary: [gdb, riscv] Ensure instructions are always fetches as LE Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: branislav.brzak at syrmia dot com Target Milestone: --- Currently riscv gdb code looks at arch byte order when fetching instructions. This works when the target is LE, but on BE arch it will byte swap the instruction, while the riscv spec defines all instructions are LE encoded regardless of system memory endianess. This is for a pending patch. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-06-21 8:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-21 8:54 branislav.brzak at syrmia dot com [this message] 2023-06-21 8:59 ` [Bug gdb/30571] " branislav.brzak at syrmia dot com 2023-06-21 16:37 ` tromey at sourceware dot 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-30571-4717@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).