public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] [BFD][AARCH64]Fix MOVW_SABS_G(0, 1, 2) relocation overflow check.
Date: Fri, 26 Feb 2016 18:19:00 -0000	[thread overview]
Message-ID: <c5e3a3641ea9d6ed2918021fd77925825d24e9be@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT c5e3a3641ea9d6ed2918021fd77925825d24e9be ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: c5e3a3641ea9d6ed2918021fd77925825d24e9be

[BFD][AARCH64]Fix MOVW_SABS_G(0,1,2) relocation overflow check.

For these three relocations, 17 bit signed value should be used, instead of
16 bit. The bitsize field is changed from 16 to 17, this field in aarch64
backend is used for overflow check only.

bfd/

2016-02-26  Renlin Li  <renlin.li@arm.com>

    * elfnn-aarch64.c (elfNN_aarch64_howto_table): Fix signed overflow
    check for MOVW_SABS_G0, MOVW_SABS_G1, MOVW_SABS_G2.

ld/

2016-02-26  Renlin Li  <renlin.li@arm.com>

    * testsuite/ld-aarch64/aarch64-elf.exp: Run new testcases.
    * testsuite/ld-aarch64/emit-relocs-270.d: Update to use new boundary.
    * testsuite/ld-aarch64/emit-relocs-271.d: Likewise.
    * testsuite/ld-aarch64/emit-relocs-272.d: Likewise.
    * testsuite/ld-aarch64/emit-relocs-270-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-270-overflow.s: New.
    * testsuite/ld-aarch64/emit-relocs-271-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-271-overflow.s: New.
    * testsuite/ld-aarch64/emit-relocs-272-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-272-overflow.s: New.


             reply	other threads:[~2016-02-26 18:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 18:19 sergiodj+buildbot [this message]
2016-02-26 18:20 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2016-02-26 18:25 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2016-02-26 18:38 ` Failures on Fedora-x86_64-cxx-build-m64, " sergiodj+buildbot
2016-02-26 18:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-02-26 18:49 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-02-26 18:54 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-02-26 19:00 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-26 19:09 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-02-26 19:19 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-02-26 21:06 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-02-26 21:45 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-02-26 22:30 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-26 23:54 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-02-27  0:14 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-02-27  0:20 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-02-27  1:03 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-27  3:18 ` Failures on Debian-i686, " sergiodj+buildbot
2016-02-27  3:19 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-02-27  3:56 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-27  4:16 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-02-27  5:06 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-02-27  9:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-27 10:14 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot

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=c5e3a3641ea9d6ed2918021fd77925825d24e9be@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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).