public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/17457] aarch64/gdbserver: wrong floating point registers display
Date: Tue, 16 Dec 2014 07:59:00 -0000	[thread overview]
Message-ID: <bug-17457-4717-B6RPNLMwju@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17457-4717@http.sourceware.org/bugzilla/>

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

--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  bf330350c212fb8880faab663f5b3565319d0a95 (commit)
      from  8fda9068191372d8282648986055493be17feff0 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=bf330350c212fb8880faab663f5b3565319d0a95

commit bf330350c212fb8880faab663f5b3565319d0a95
Author: Catalin Udma <catalin.udma@freescale.com>
Date:   Tue Dec 16 09:51:42 2014 +0200

    aarch64/gdbserver: fix floating point registers display

    When using aarch64 gdb with gdbserver, floating point registers are
    not correctly displayed, as below:
      (gdb) info registers fpsr fpcr
      fpsr           <unavailable>
      fpcr           <unavailable>

    To fix these problems, the missing fpsr and fpcr registers are added
    when floating point registers are read/write
    Add test for aarch64 floating point
    PR server/17457

    gdb/gdbserver/

        PR server/17457
        * linux-aarch64-low.c (AARCH64_FPSR_REGNO): New define.
        (AARCH64_FPCR_REGNO): Likewise.
        (AARCH64_NUM_REGS): Update to include fpsr/fpcr registers.
        (aarch64_fill_fpregset): Add missing fpsr/fpcr registers.
        (aarch64_store_fpregset): Likewise.

    gdb/testsuite/

        PR server/17457
        * gdb.arch/aarch64-fp.c: New file.
        * gdb.arch/aarch64-fp.exp: New file.

    Signed-off-by: Catalin Udma <catalin.udma@freescale.com>

-----------------------------------------------------------------------

Summary of changes:
 gdb/gdbserver/ChangeLog               |    9 ++++
 gdb/gdbserver/linux-aarch64-low.c     |    8 +++-
 gdb/testsuite/ChangeLog               |    6 ++
 gdb/testsuite/gdb.arch/aarch64-fp.c   |   38 +++++++++++++++
 gdb/testsuite/gdb.arch/aarch64-fp.exp |   85 +++++++++++++++++++++++++++++++++
 5 files changed, 145 insertions(+), 1 deletions(-)
 create mode 100644 gdb/testsuite/gdb.arch/aarch64-fp.c
 create mode 100644 gdb/testsuite/gdb.arch/aarch64-fp.exp

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


  parent reply	other threads:[~2014-12-16  7:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06  9:02 [Bug server/17457] New: " catalin.udma at freescale dot com
2014-10-06  9:03 ` [Bug server/17457] " catalin.udma at freescale dot com
2014-10-06 14:12 ` palves at redhat dot com
2014-10-06 14:21 ` catalin.udma at freescale dot com
2014-10-06 14:30 ` palves at redhat dot com
2014-10-06 14:48 ` catalin.udma at freescale dot com
2014-10-06 14:53 ` palves at redhat dot com
2014-10-06 15:00 ` catalin.udma at freescale dot com
2014-10-08 12:27 ` catalin.udma at freescale dot com
2014-12-16  7:59 ` cvs-commit at gcc dot gnu.org [this message]
2015-02-24 22:22 ` qiyao at gcc dot gnu.org
2015-02-25 10:53 ` catalin.udma at freescale dot com
2015-02-25 13:25 ` qiyao at gcc dot gnu.org
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-17457-4717-B6RPNLMwju@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).