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] [ARM] Add armelf_linux_fdpiceabi and armelfb_linux_fdpiceabi BFD backends
Date: Wed, 25 Apr 2018 21:40:00 -0000	[thread overview]
Message-ID: <617a5ada88c7d4b6aae201ad5b295f3d2ef07c10@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 617a5ada88c7d4b6aae201ad5b295f3d2ef07c10 ***

Author: Christophe Lyon <christophe.lyon@st.com>
Branch: master
Commit: 617a5ada88c7d4b6aae201ad5b295f3d2ef07c10

[ARM] Add armelf_linux_fdpiceabi and armelfb_linux_fdpiceabi BFD backends

Initial definition of these new backends.

2018-04-25  Christophe Lyon  <christophe.lyon@st.com>
	Mickal Gun  <mickael.guene@st.com>

	bfd/
	* config.bfd (arm*-*-linux-*): Add arm_elf32_fdpic_be_vec and
	arm_elf32_fdpic_le_vec to targ_selvecs. Accept
	arm*-*-uclinuxfdpiceabi.
	* configure.ac: Add support for arm_elf32_fdpic_be_vec and
	arm_elf32_fdpic_le_vec.
	* configure: Regenerate.
	* elf32-arm.c (struct elf32_arm_link_hash_table): Add fdpic_p.
	(elf32_arm_link_hash_table_create): Initialize fdpic_p.
	(TARGET_LITTLE_SYM, TARGET_LITTLE_NAME, TARGET_BIG_SYM)
	(TARGET_BIG_NAME, elf_match_priority): Define for FDPIC targets.
	(elf32_arm_fdpic_link_hash_table_create): New.
	* targets.c (_bfd_target_vector): Add arm_elf32_fdpic_be_vec and
	arm_elf32_fdpic_le_vec.

	ld/
	* Makefile.am (ALL_EMULATION_SOURCES): Add
	earmelf_linux_fdpiceabi.c and earmelfb_linux_fdpiceabi.c.
	(earmelf_linux_fdpiceabi.c, earmelfb_linux_fdpiceabi.c): New rules.
	* Makefile.in: Regenerate.
	* configure.tgt (arm*-*-uclinuxfdpiceabi): Handle new target.
	* emulparams/armelf_linux_fdpiceabi.sh: New.
	* emulparams/armelfb_linux_fdpiceabi.sh: New.


             reply	other threads:[~2018-04-25 21:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 21:40 sergiodj+buildbot [this message]
2018-04-25 21:40 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot
2018-04-25 21:40 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-04-25 21:43 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-04-25 21:55 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-04-25 21:58 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2018-04-25 22:03 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-04-25 22:05 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-04-25 22:05 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-04-25 22:13 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2018-04-25 22:16 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-04-25 22:20 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-04-25 22:50 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-04-25 23:36 ` Failures on Ubuntu-AArch32-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=617a5ada88c7d4b6aae201ad5b295f3d2ef07c10@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).