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] Introduce enum_flag type for ui_out flags
Date: Fri, 02 Dec 2016 22:35:00 -0000 [thread overview]
Message-ID: <bef721e278d9ba3178e679eda38ac86ef2dc0d5d@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT bef721e278d9ba3178e679eda38ac86ef2dc0d5d ***
Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: bef721e278d9ba3178e679eda38ac86ef2dc0d5d
Introduce enum_flag type for ui_out flags
This patch changes the ui_out flags to be an enum flag.
gdb/ChangeLog:
* ui-out.h: Include "common/enum-flags.h".
(enum ui_flags): Rename to ...
(enum ui_out_flag): ... this.
(ui_out_flags): Define enum flag type.
(ui_out_test_flags): Change type of parameter to ui_out_flags.
(ui_out_new): Likewise.
* ui-out.c (ui_out_test_flags): Likewise.
(ui_out_new): Likewise.
* cli-out.c (cli_out_new): Update variable type.
* mi/mi-out.c (mi_out_new): Likewise.
* tui/tui-out.c (tui_out_new): Likewise.
next reply other threads:[~2016-12-02 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 22:35 sergiodj+buildbot [this message]
2016-12-02 22:37 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot
2016-12-02 23:09 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2016-12-02 23:22 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-12-02 23:23 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-12-10 18:30 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-12-10 18:47 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-12-10 19:17 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-12-16 12:47 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-12-16 12:50 ` Failures on Fedora-ppc64le-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=bef721e278d9ba3178e679eda38ac86ef2dc0d5d@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: link
Be 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).