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] Propagate gdb_disassembly_flags to btrace_print_lines Date: Mon, 05 Mar 2018 01:19:00 -0000 [thread overview] Message-ID: <3dea1ef72c646d808e5b287e98253f3b8670c450@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 3dea1ef72c646d808e5b287e98253f3b8670c450 *** Author: Simon Marchi <simon.marchi@polymtl.ca> Branch: master Commit: 3dea1ef72c646d808e5b287e98253f3b8670c450 Propagate gdb_disassembly_flags to btrace_print_lines This function can take the flags as the gdb_disassembly_flags type instead of int. gdb/ChangeLog: * record-btrace.c (btrace_print_lines): Change type of flags to gdb_disassembly_flags.
next reply other threads:[~2018-03-05 1:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-05 1:19 sergiodj+buildbot [this message] 2018-03-05 1:19 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-03-05 1:20 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-03-05 1:25 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-03-05 1:28 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-03-05 1:32 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-05 1:41 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-05 1:47 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-03-05 1:57 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-03-05 1:58 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-03-05 2:41 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2018-03-07 9:25 ` Failures on Ubuntu-AArch64-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=3dea1ef72c646d808e5b287e98253f3b8670c450@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).