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 tdep/7670] arm_print_float_info using printf() and read_register()
Date: Tue, 05 Nov 2013 09:19:00 -0000	[thread overview]
Message-ID: <bug-7670-4717-ijgqsKpD4T@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-7670-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=7670

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
       via  12b272760b8ed06ee64f4b6ce52eb9beeed35841 (commit)
      from  dba6fa9bce92c9f9fcca07269ac8443797bd9338 (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=12b272760b8ed06ee64f4b6ce52eb9beeed35841

commit 12b272760b8ed06ee64f4b6ce52eb9beeed35841
Author: Will Newton <will.newton@linaro.org>
Date:   Fri Nov 1 17:44:19 2013 -0700

    gdb/arm-tdep.c: Use filtered output in arm_print_float_info.

    gdb/ChangeLog:

    2013-11-05  Will Newton  <will.newton@linaro.org>

        PR gdb/7670
        * arm-tdep.c (print_fpu_flags): Use filtered output routines.
        (arm_print_float_info): Likewise.

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

Summary of changes:
 gdb/ChangeLog  |    6 ++++++
 gdb/arm-tdep.c |   26 +++++++++++++-------------
 2 files changed, 19 insertions(+), 13 deletions(-)

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


       reply	other threads:[~2013-11-05  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-7670-4717@http.sourceware.org/bugzilla/>
2013-11-05  9:19 ` cvs-commit at gcc dot gnu.org [this message]
2013-11-05  9:23 ` will.newton at gmail 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-7670-4717-ijgqsKpD4T@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).