public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ashi08104 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/17296] New: gdb can't print neon register correctly on aarch64
Date: Thu, 21 Aug 2014 05:58:00 -0000	[thread overview]
Message-ID: <bug-17296-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=17296

            Bug ID: 17296
           Summary: gdb can't print neon register correctly on aarch64
           Product: gdb
           Version: 7.8
            Status: NEW
          Severity: critical
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: ashi08104 at gmail dot com

Created attachment 7753
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7753&action=edit
neon example

Hi, there:
When debugging code on aarch64, I find gdb can't print neon register correctly.
I've a simple example attached:

#define SIZE 8
int main(void)
{
  char arr[SIZE] = {0, 1, 2, 3, 4, 5, 6, 7};
  asm volatile("ld1 {v0.8b}, [%0], 8"::"r"(arr):"v0", "memory");
}

after running the 'ld1' instruction, the v0.8b value in gdb is:
  s = {4, 5, 6, 7, 0 <repeats 12 times>}
While the true value should be:
  s = {0, 1, 2, 3, 4, 5, 6, 7}

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2014-08-21  5:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21  5:58 ashi08104 at gmail dot com [this message]
2014-08-21  7:00 ` [Bug server/17296] " ashi08104 at gmail dot com
2015-10-13 20:51 ` jmgao at google 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-17296-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: 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).