This is the mail archive of the binutils-cvs@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gdb and binutils branch master updated. a35d5e823fdfe8a6e7e05ca8e3fb8bb5697335b1


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  a35d5e823fdfe8a6e7e05ca8e3fb8bb5697335b1 (commit)
      from  483805cf9ea5a6dace41415d8830e93fccc49c43 (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=a35d5e823fdfe8a6e7e05ca8e3fb8bb5697335b1

commit a35d5e823fdfe8a6e7e05ca8e3fb8bb5697335b1
Author: Max Filippov <jcmvbkbc@gmail.com>
Date:   Tue Apr 15 19:12:46 2014 +0400

    Fix alignment for the first section frag on xtensa
    
    Linking object files produced by partial linking with link-time
    relaxation enabled sometimes fails with the following error message:
    
    dangerous relocation: call8: misaligned call target: (.text.unlikely+0x63)
    
    This happens because no basic block with an XTENSA_PROP_ALIGN flag in the
    property table is generated for the first basic block, even if the
    .align directive is present.
    It was believed that the first frag alignment could be derived from the
    section alignment, but this was not implemented for the partial linking
    case: after partial linking first frag of a section may become not
    first, but no additional alignment frag is inserted before it.
    Basic block for such frag may be merged with previous basic block into
    extended basic block during relaxation pass losing its alignment
    restrictions.
    
    Fix this by always recording alignment for the first section frag.
    
    2014-04-22  Max Filippov  <jcmvbkbc@gmail.com>
    
    gas/
        * config/tc-xtensa.c (xtensa_handle_align): record alignment for the
        first section frag.
    
    gas/testsuite/
        * gas/xtensa/all.exp: Add test for the first section frag alignment.
        * gas/xtensa/first_frag_align.d: First section frag alignment expected
        dump.
        * gas/xtensa/first_frag_align.s: First section frag alignment test
        source.

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

Summary of changes:
 gas/ChangeLog                               |    5 +++++
 gas/config/tc-xtensa.c                      |    1 -
 gas/testsuite/ChangeLog                     |    8 ++++++++
 gas/testsuite/gas/xtensa/all.exp            |    1 +
 gas/testsuite/gas/xtensa/first_frag_align.d |    9 +++++++++
 gas/testsuite/gas/xtensa/first_frag_align.s |    5 +++++
 6 files changed, 28 insertions(+), 1 deletions(-)
 create mode 100644 gas/testsuite/gas/xtensa/first_frag_align.d
 create mode 100644 gas/testsuite/gas/xtensa/first_frag_align.s


hooks/post-receive
-- 
gdb and binutils


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]