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] FDPIC: Add stack segment Date: Thu, 26 Apr 2018 01:29:00 -0000 [thread overview] Message-ID: <cb10292c2a6c26349c02ec275e4087147fd1cdf0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT cb10292c2a6c26349c02ec275e4087147fd1cdf0 *** Author: Christophe Lyon <christophe.lyon@st.com> Branch: master Commit: cb10292c2a6c26349c02ec275e4087147fd1cdf0 [ARM] FDPIC: Add stack segment The size of the stack segment defaults to 32KB, and can be overridden by defining the __stacksize symbol. 2018-04-25 Christophe Lyon <christophe.lyon@st.com> Mickal Gun <mickael.guene@st.com> bfd/ * elf32-arm.c (DEFAULT_STACK_SIZE): New. (elf32_arm_always_size_sections): Create stack segment.
next reply other threads:[~2018-04-26 1:14 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-26 1:29 sergiodj+buildbot [this message] 2018-04-26 1:14 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-04-26 1:48 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-04-26 2:30 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-04-26 3:02 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-04-26 3:06 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-04-26 3:06 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-26 3:30 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot 2018-04-26 5:59 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-04-26 13:05 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-26 13:49 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-04-26 14:33 ` 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=cb10292c2a6c26349c02ec275e4087147fd1cdf0@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).