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] format_pieces-selftests.c: Silence ARI warnings Date: Fri, 18 May 2018 22:33:00 -0000 [thread overview] Message-ID: <1d143c36eedc0f0b124e6aa6fb3b98b1e6ff74b0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 1d143c36eedc0f0b124e6aa6fb3b98b1e6ff74b0 *** Author: Simon Marchi <simon.marchi@ericsson.com> Branch: master Commit: 1d143c36eedc0f0b124e6aa6fb3b98b1e6ff74b0 format_pieces-selftests.c: Silence ARI warnings Silence this: unittests/format_pieces-selftests.c:51: warning: code: Do not use printf("%ll"), instead use printf("%s",phex()) to dump a `long long' value unittests/format_pieces-selftests.c:56: warning: code: Do not use printf("%ll"), instead use printf("%s",phex()) to dump a `long long' value gdb/ChangeLog: * unittests/format_pieces-selftests.c (test_format_specifier): Add ARI comments.
next reply other threads:[~2018-05-18 20:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-18 22:33 sergiodj+buildbot [this message] 2018-05-18 22:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2018-05-19 4:54 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-05-19 5:25 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-05-24 13:36 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-05-24 15:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-05-24 15:49 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-07-15 20:06 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master sergiodj+buildbot 2018-07-16 2:40 ` Failures on Ubuntu-AArch32-native-gdbserver-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=1d143c36eedc0f0b124e6aa6fb3b98b1e6ff74b0@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).