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: Add TLS_TRANSITION_IE_TO_LE_P
Date: Fri, 06 Oct 2017 07:18:00 -0000 [thread overview]
Message-ID: <51537393bd939e79f6e9291629fb65a17e6f19da@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 51537393bd939e79f6e9291629fb65a17e6f19da ***
Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 51537393bd939e79f6e9291629fb65a17e6f19da
x86: Add TLS_TRANSITION_IE_TO_LE_P
Add TLS_TRANSITION_IE_TO_LE_P which returns TRUE if TLS IE->LE transition
is OK.
* elfxx-x86.h (TLS_TRANSITION_IE_TO_LE_P): New.
* elf32-i386.c (elf_i386_tls_transition): Use it.
* elf64-x86-64.c (elf_x86_64_tls_transition): Likewise.
next reply other threads:[~2017-10-06 7:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 7:18 sergiodj+buildbot [this message]
2017-10-06 7:50 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, branch master sergiodj+buildbot
2017-10-06 8:02 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-06 8:07 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2017-10-06 8:10 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-10-06 8:18 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-06 8:33 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-20 1:58 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2017-10-20 8:29 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-10-23 23:40 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2017-10-24 8:57 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2017-10-24 9:37 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2017-10-24 18:52 ` Failures on Fedora-ppc64le-native-extended-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=51537393bd939e79f6e9291629fb65a17e6f19da@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).