public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com To: gdb-testers@sourceware.org Subject: [binutils-gdb] Don't add the zlib header to SHF_COMPRESSED section Date: Thu, 14 May 2015 23:16:00 -0000 [thread overview] Message-ID: <dab394de9e41de54df5e2310e081e1c550326f5b@kwanyin> (raw) *** TEST RESULTS FOR COMMIT dab394de9e41de54df5e2310e081e1c550326f5b *** Author: H.J. Lu <hjl.tools@gmail.com> Branch: master Commit: dab394de9e41de54df5e2310e081e1c550326f5b Don't add the zlib header to SHF_COMPRESSED section In a SHF_COMPRESSED compressed section, the raw compressed data should begin immediately after the compression header. This patch removes the extra zlib header from the SHF_COMPRESSED section. bfd/ * bfd.c (bfd_update_compression_header): Also write the zlib header if the SHF_COMPRESSED bit cleared.. (bfd_check_compression_header): Return the uncompressed size. * compress.c (decompress_contents): Don't skip the zlib header. (bfd_compress_section_contents): Properly handle ELFCOMPRESS_ZLIB, which doesn't have the zlib header. (bfd_init_section_decompress_status): Likewise. (bfd_get_full_section_contents): Updated. (bfd_is_section_compressed): Likewise. (bfd_is_section_compressed_with_header): Return the uncompressed size. * elf.c (_bfd_elf_make_section_from_shdr): Updated. * bfd-in2.h: Regenerated. binutils/ * readelf.c (uncompress_section_contents): Add a parameter for uncompressed size. Don't check the zlib header. (load_specific_debug_section): Updated. binutils/testsuite/ * binutils-all/compress.exp: Replace "$OBJDUMP -s -j .debug_info" with "$OBJDUMP -W". * binutils-all/libdw2-compressedgabi.out: Updated. gas/ 2015-05-14 H.J. Lu <hongjiu.lu@intel.com> * write.c (compress_debug): Don't write the zlib header, which is handled by bfd_update_compression_header.
next reply other threads:[~2015-05-14 23:16 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-14 23:16 sergiodj+buildbot [this message] 2015-05-14 23:16 ` Failures on Fedora-ppc64be-cc-with-index, branch master sergiodj+buildbot 2015-05-14 23:22 ` Failures on Debian-i686, " sergiodj+buildbot 2015-05-14 23:46 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-05-15 0:03 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2015-05-15 1:22 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-05-15 2:05 ` Failures on Fedora-i686, " sergiodj+buildbot 2015-05-15 2:37 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2015-05-15 2:38 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2015-05-15 2:42 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2015-05-15 3:08 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-05-15 3:42 ` Failures on Fedora-x86_64-native-gdbserver-m32, " 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=dab394de9e41de54df5e2310e081e1c550326f5b@kwanyin \ --to=sergiodj+buildbot@redhat.com \ --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).