public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "petemoore at gmx dot net" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29471] New: gdb 12.1 'i r' command doesn't recognise register NZCV under target aarch64 Date: Thu, 11 Aug 2022 12:10:29 +0000 [thread overview] Message-ID: <bug-29471-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29471 Bug ID: 29471 Summary: gdb 12.1 'i r' command doesn't recognise register NZCV under target aarch64 Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: petemoore at gmx dot net Target Milestone: --- In AArch64 state, there is no Current Program Status Register (CPSR). You can access the different components of the traditional CPSR independently as the following Process State fields: N, Z, C, and V condition flags (NZCV). Current register width (nRW). Stack pointer selection bit (SPSel). Interrupt disable flags (DAIF). Current exception level (EL). Single step process state bit (SS). Illegal exception return state bit (IL). See: https://developer.arm.com/documentation/dui0801/a/Overview-of-AArch64-state/Process-State However, when I display registers in gdb, nzcv is not shown, and cpsr is: ``` (gdb) i r x0 0x43 67 x1 0xe23d402b356d3bce -2144487293234365490 x2 0x5a4d387e567f030 406682446993027120 x3 0x5a 90 x4 0x27a2 10146 x5 0x5a 90 x6 0x43 67 x7 0x756e89b103df671c 8461852143242929948 x8 0x624d1246a62939a9 7083337883568388521 x9 0x1b1af900032c1cc8 1953147166867070152 x10 0x8bc19566de54593a -8376249562883139270 x11 0x184366151d3c3a4a 1748353321220717130 x12 0x18edff72c0631cb3 1796372694709771443 x13 0x26ac09d83f16143a 2786613093811491898 x14 0x55342216197e994b 6139569670325180747 x15 0xe28fed9e950e9254 -2121215634106838444 x16 0xaf56554915dfd8ef -5812364496687081233 x17 0xbac3e3a52a18a9b7 -4988893663681009225 x18 0x91077f6feafd18b 653153848687317387 x19 0x98a0474a818d0bdb -7448875398344143909 x20 0xe05fa2ada09bcaba -2278924019818575174 x21 0x608e95a84113f94 434853939013304212 x22 0xd56ed339042e92f3 -3067282054355971341 x23 0x3bb6d74d34f84b97 4302863220600228759 x24 0xd860f821d113d545 -2855009339627547323 x25 0x2a78b30673bda2f7 3060392787091235575 x26 0x30b04bd9c590e740 3508387508416210752 x27 0x98d07855f9e2b0c2 -7435310674128752446 x28 0x211a0 135584 x29 0x3bfffc50 1006632016 x30 0x230c 8972 sp 0x3bfffc50 0x3bfffc50 pc 0x2438 0x2438 <print_w0> cpsr 0x200003cd [ SP EL=3 F I A D BTYPE=0 C ] fpsr 0x0 [ ] fpcr 0x0 [ RMode=0 ] ``` Furthermore, if I try to inspect the nzcv register, I get an error: ``` (gdb) i r nzcv Invalid register `nzcv' ``` This is gdb 12.1, built from source and configured with `--target=aarch64-none-elf` running under ubuntu 20.04. Many thanks. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-08-11 12:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-11 12:10 petemoore at gmx dot net [this message] 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 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@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).