bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/16694] gas does not accept ARM VFP registers in .cfi_offset dir


From: cvs-commit at gcc dot gnu.org
Subject: [Bug gas/16694] gas does not accept ARM VFP registers in .cfi_offset directives
Date: Mon, 17 Mar 2014 16:32:05 +0000

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

--- Comment #3 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  1f5afe1cc03bb2cd50b75a21d491a349d7011ea1 (commit)
      from  f7c77d9323a3dcd6e52a8038d0cdab0748e5bc62 (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=1f5afe1cc03bb2cd50b75a21d491a349d7011ea1

commit 1f5afe1cc03bb2cd50b75a21d491a349d7011ea1
Author: Nick Clifton <address@hidden>
Date:   Mon Mar 17 16:30:30 2014 +0000

    Add support for parsing VFP register names in .cfi_offset directives.

        PR gas/16694
        * config/tc-arm.c (tc_arm_regname_to_dw2regnum): Parse VFP
        registers as well.

        * gas/cfi/cfi-arm-1.s: Add checks of VFP registers.
        * gas/cfi/cfi-arm-1.d: Update expected output.

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

Summary of changes:
 gas/ChangeLog                     |    6 ++++++
 gas/config/tc-arm.c               |   29 +++++++++++++++++++++++------
 gas/testsuite/ChangeLog           |    6 ++++++
 gas/testsuite/gas/cfi/cfi-arm-1.d |    9 +++++++--
 gas/testsuite/gas/cfi/cfi-arm-1.s |    6 ++++++
 5 files changed, 48 insertions(+), 8 deletions(-)

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]