public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29471] gdb 12.1 'i r' command doesn't recognise register NZCV under target aarch64-none-elf Date: Fri, 21 Oct 2022 14:30:23 +0000 [thread overview] Message-ID: <bug-29471-4717-akxPgsefpH@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29471-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29471 --- Comment #3 from Luis Machado <luis.machado at arm dot com> --- Hi Pete, I don't think there is anything wrong with QEMU or GDB. You can find all the bits you described in the CPSR. The CPSR is described like so: <flags id="cpsr_flags" size="4"> <!-- Stack Pointer. --> <field name="SP" start="0" end="0"/> <!-- Exception Level. --> <field name="EL" start="2" end="3"/> <!-- Execution state. --> <field name="nRW" start="4" end="4"/> <!-- FIQ interrupt mask. --> <field name="F" start="6" end="6"/> <!-- IRQ interrupt mask. --> <field name="I" start="7" end="7"/> <!-- SError interrupt mask. --> <field name="A" start="8" end="8"/> <!-- Debug exception mask. --> <field name="D" start="9" end="9"/> <!-- ARMv8.5-A: Branch Target Identification BTYPE. --> <field name="BTYPE" start="10" end="11"/> <!-- ARMv8.0-A: Speculative Store Bypass. --> <field name="SSBS" start="12" end="12"/> <!-- Illegal Execution state. --> <field name="IL" start="20" end="20"/> <!-- Software Step. --> <field name="SS" start="21" end="21"/> <!-- ARMv8.1-A: Privileged Access Never. --> <field name="PAN" start="22" end="22"/> <!-- ARMv8.2-A: User Access Override. --> <field name="UAO" start="23" end="23"/> <!-- ARMv8.4-A: Data Independent Timing. --> <field name="DIT" start="24" end="24"/> <!-- ARMv8.5-A: Tag Check Override. --> <field name="TCO" start="25" end="25"/> <!-- Overflow Condition flag. --> <field name="V" start="28" end="28"/> <!-- Carry Condition flag. --> <field name="C" start="29" end="29"/> <!-- Zero Condition flag. --> <field name="Z" start="30" end="30"/> <!-- Negative Condition flag. --> <field name="N" start="31" end="31"/> </flags> <reg name="cpsr" bitsize="32" type="cpsr_flags"/> For the 1-bit fields, GDB will show the field name if the bit is 1. Otherwise nothing will be shown. So in your example... --- cpsr 0x200003cd [ SP EL=3 F I A D BTYPE=0 C ] --- You can see the various bits that are set. For fields with more than a single bit, you will see the value, like BTYPE. Does that clarify things? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-21 14:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-11 12:10 [Bug gdb/29471] New: gdb 12.1 'i r' command doesn't recognise register NZCV under target aarch64 petemoore at gmx dot net 2022-08-11 15:07 ` [Bug gdb/29471] gdb 12.1 'i r' command doesn't recognise register NZCV under target aarch64-none-elf petemoore at gmx dot net 2022-10-21 10:06 ` luis.machado at arm dot com 2022-10-21 12:42 ` petemoore at gmx dot net 2022-10-21 14:30 ` luis.machado at arm dot com [this message] 2022-11-03 9:22 ` cvs-commit at gcc dot gnu.org 2022-12-05 15:37 ` luis.machado at arm dot com
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-29471-4717-akxPgsefpH@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).