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] MIPS/BFD: Keep EI_ABIVERSION setting together
Date: Thu, 21 Jun 2018 21:11:00 -0000 [thread overview]
Message-ID: <334cd8a780840d6aee86790fe2fe5f02fe56edf6@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 334cd8a780840d6aee86790fe2fe5f02fe56edf6 ***
Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 334cd8a780840d6aee86790fe2fe5f02fe56edf6
MIPS/BFD: Keep EI_ABIVERSION setting together
Shuffle code in `_bfd_mips_post_process_headers' so that the setting of
the EI_ABIVERSION ELF file header field is complete before calling
`_bfd_elf_post_process_headers'. This used to be the case, but was
changed with commit 351cdf24d223 ("[MIPS] Implement O32 FPXX, FP64 and
FP64A ABI extensions") for no reason.
bfd/
* elfxx-mips.c (_bfd_mips_post_process_headers): Keep
EI_ABIVERSION setting together.
next reply other threads:[~2018-06-21 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 21:11 sergiodj+buildbot [this message]
2018-06-21 21:20 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-06-21 22:01 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-06-21 22:35 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-06-21 22:36 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-06-21 22:39 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-06-21 22:58 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-06-21 23:00 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-06-21 23:11 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2018-06-21 23:19 ` Failures on Debian-s390x-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=334cd8a780840d6aee86790fe2fe5f02fe56edf6@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).