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] Fix PR ld/20545 - relaxation bugs in avr backend Date: Tue, 06 Sep 2016 18:00:00 -0000 [thread overview] Message-ID: <bf1865065f64af2f32798c0327143baf99634e8d@gdb-build> (raw) *** TEST RESULTS FOR COMMIT bf1865065f64af2f32798c0327143baf99634e8d *** Author: Senthil Kumar Selvaraj <senthil_kumar.selvaraj@atmel.com> Branch: master Commit: bf1865065f64af2f32798c0327143baf99634e8d Fix PR ld/20545 - relaxation bugs in avr backend Prior to the patch, addends for relocs were being adjusted even if they went beyond an alignment boundary. This is wrong - to preserve alignment constraints, the relaxation logic adds as many padding bytes at the alignment boundary as was deleted, so addends beyond the boundary should not be adjusted. avr-prop-7.s reproduces this scenario. Also, prior to this patch, the relaxation logic assumed that the addr parameter pointed to the middle of the instruction to be deleted, and that addr - count would therefore be the shrinked instruction's address. This is true when actually shrinking instructions. The alignment constraints handling logic also invokes the same logic though, with addr as the starting offset of padding bytes and with count as the number of bytes to be deleted. Calculating the shrinked insn's address as addr - count is obviously wrong in this case - that offset would point to count bytes before the last non-padded byte. avr-prop-8.s reproduces this scenario. To fix scenario 1, the patch adds an additional check to ensure reloc addends aren't adjusted if they cross a shrink boundary. The shrink boundary is either the section size or an alignment boundary. Addends pointing at an alignment boundary don't need to be adjusted, as padding would occur and keep the boundary the same. Addends pointing at section size need to be adjusted though, as no padding occurs and the section size itself would get decremented. The patch records whether padding occured (did_pad) and uses that to detect and handle this condition. To fix scenario 2, the patch adds an additional parameter (delete_shrinks_insn) to elf32_avr_relax_delete_bytes to distinguish instruction bytes deletion from padding bytes deletion. It then uses that to correctly set shrinked_insn_address. bfd/ChangeLog: 2016-09-02 Senthil Kumar Selvaraj <senthil_kumar.selvaraj@atmel.com> PR ld/20545 * elf32-avr.c (elf32_avr_relax_delete_bytes): Add parameter delete_shrinks_insn. Modify computation of shrinked_insn_address. Compute shrink_boundary and adjust addend only if addend_within_shrink_boundary. (elf32_avr_relax_section): Modify calls to elf32_avr_relax_delete_bytes to pass extra parameter. ld/ChangeLog: 2016-09-02 Senthil Kumar Selvaraj <senthil_kumar.selvaraj@atmel.com> PR ld/20545 * testsuite/ld-avr/avr-prop-7.d: New test. * testsuite/ld-avr/avr-prop-7.s: New test. * testsuite/ld-avr/avr-prop-8.d: New test. * testsuite/ld-avr/avr-prop-8.s: New test.
next reply other threads:[~2016-09-06 7:20 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-09-06 18:00 sergiodj+buildbot [this message] 2016-09-06 18:00 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch master sergiodj+buildbot 2016-09-06 18:14 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2016-09-06 18:15 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2016-09-06 18:20 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-06 18:20 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-09-06 18:22 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2016-09-06 18:25 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-06 18:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-06 18:38 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-06 18:43 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-09-06 18:44 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-06 18:48 ` Failures on Fedora-ppc64le-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=bf1865065f64af2f32798c0327143baf99634e8d@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: linkBe 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).