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] x86: Don't change r_type when performing TLS transitions Date: Wed, 06 Sep 2017 13:09:00 -0000 [thread overview] Message-ID: <419414eafcee7cd749ee4622ef25020e48b52cc4@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 419414eafcee7cd749ee4622ef25020e48b52cc4 *** Author: H.J. Lu <hjl.tools@gmail.com> Branch: master Commit: 419414eafcee7cd749ee4622ef25020e48b52cc4 x86: Don't change r_type when performing TLS transitions Don't change r_type when performing TLS transitions to avoid getting the relocation type with ELF32_R_TYPE again. * elf32-i386.c (elf_i386_relocate_section): Don't change r_type when calling elf_i386_tls_transition. Don't use ELF32_R_TYPE to get the relocation type again. * elf64-x86-64.c (elf_x86_64_relocate_section): Don't change r_type when calling elf_x86_64_tls_transition. Don't use ELF32_R_TYPE to get the relocation type again.
next reply other threads:[~2017-09-06 12:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-06 13:09 sergiodj+buildbot [this message] 2017-09-06 13:55 ` Failures on Fedora-s390x-m64, branch master 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=419414eafcee7cd749ee4622ef25020e48b52cc4@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).