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] Change type of cpsr in arm_sigreturn_next_pc Date: Thu, 05 May 2016 08:19:00 -0000 [thread overview] Message-ID: <cf2ebb6e0958c9193c7c65620cd7a8b990d8b316@gdb-build> (raw) *** TEST RESULTS FOR COMMIT cf2ebb6e0958c9193c7c65620cd7a8b990d8b316 *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: cf2ebb6e0958c9193c7c65620cd7a8b990d8b316 Change type of cpsr in arm_sigreturn_next_pc Variable cpsr holds the value of cpsr register, which is 32-bit. It is better to explicitly use uint32_t. gdb/gdbserver: 2016-05-05 Yao Qi <yao.qi@linaro.org> * linux-arm-low.c (arm_sigreturn_next_pc): Change type of cpsr to uint32_t.
next reply other threads:[~2016-05-05 8:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-05 8:19 sergiodj+buildbot [this message] 2016-05-05 8:19 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot 2016-05-05 8:27 ` Failures on Debian-i686, " sergiodj+buildbot 2016-05-05 8:28 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-05-05 8:35 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2016-05-05 8:41 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2016-05-05 8:55 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-05-05 9:09 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-05-05 9:24 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-05-05 9:26 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-05-05 9:30 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot 2016-05-05 9:50 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2016-05-05 10:02 ` Failures on Fedora-ppc64be-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=cf2ebb6e0958c9193c7c65620cd7a8b990d8b316@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).