public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "catalin.udma at freescale dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/17457] aarch64/gdbserver: wrong floating point registers display
Date: Mon, 06 Oct 2014 14:21:00 -0000	[thread overview]
Message-ID: <bug-17457-4717-qAcq8rUE1Y@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 #2 from Catalin Udma <catalin.udma at freescale dot com> ---
Hi,

Actually in the bug I described two problems:
- one is wrong v0-v31 offset -> this is fixed in bdc1441
- the second is that fpsr and fpcr registers are missing: this is fixed in
bdc1441 + the patch I sent (aarch64/gdbserver: fix floating point registers
display)

Regards,
Catalin

> -----Original Message-----
> From: gdb-prs-owner@sourceware.org [mailto:gdb-prs-owner@sourceware.org]
> On Behalf Of palves at redhat dot com
> Sent: Monday, October 06, 2014 5:12 PM
> To: gdb-prs@sourceware.org
> Subject: [Bug server/17457] aarch64/gdbserver: wrong floating point
> registers display
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=17457
> 
> Pedro Alves <palves at redhat dot com> changed:
> 
>            What    |Removed                     |Added
> -------------------------------------------------------------------------
> ---
>              Status|NEW                         |RESOLVED
>                  CC|                            |palves at redhat dot com
>          Resolution|---                         |FIXED
>    Target Milestone|---                         |7.9
> 
> --- Comment #1 from Pedro Alves <palves at redhat dot com> ---
> This is fixed in both master and 7.8.1, by:
> 
> commit bdc144174bcb11e808b4e73089b850cf9620a7ee
> ...
>     Aarch64: Make CPSR a 32-bit register again in the target description
> 
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

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


  parent reply	other threads:[~2014-10-06 14:21 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 [this message]
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
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-qAcq8rUE1Y@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).