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 value_contents_eq return bool Date: Fri, 24 Nov 2017 11:34:00 -0000 [thread overview] Message-ID: <98ead37e9735438986934f9f1f35f020a093fe07@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 98ead37e9735438986934f9f1f35f020a093fe07 *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: 98ead37e9735438986934f9f1f35f020a093fe07 Change value_contents_eq return bool This patch changes value_contents_eq return type from int to bool. gdb: 2017-11-24 Yao Qi <yao.qi@linaro.org> * mi/mi-main.c (register_changed_p): Update. * value.c (value_contents_bits_eq): Change return type. (value_contents_eq): Likewise. * value.h: Update comments.
next reply other threads:[~2017-11-24 11:34 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-24 11:34 sergiodj+buildbot [this message] 2017-11-24 11:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-11-24 11:47 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-11-24 12:07 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-11-24 12:07 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-11-24 12:23 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-11-24 12:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-11-24 12:28 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-11-24 12:28 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-11-24 12:30 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-11-24 12:54 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-11-24 12:57 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-11-24 13:19 ` 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=98ead37e9735438986934f9f1f35f020a093fe07@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).