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] Remove interp_name
Date: Fri, 25 May 2018 20:59:00 -0000 [thread overview]
Message-ID: <da505cff6e29b18244dc9f6886bcb4d436263dee@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT da505cff6e29b18244dc9f6886bcb4d436263dee ***
Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: da505cff6e29b18244dc9f6886bcb4d436263dee
Remove interp_name
This removes the interp_name function. It is only used a few spots --
one of which was only calling it on "this". It's simpler to remove
it; and should class interp become opaque in the future, it will be
just as easy to update the two remaining spots to use an accessor.
ChangeLog
2018-05-25 Tom Tromey <tom@tromey.com>
* interps.c (interp_name): Remove.
* mi/mi-interp.c (mi_interp::init): Update.
* interps.h (interp_name): Remove.
(~scoped_restore_interp): Update.
* tui/tui.c (tui_enable): Update.
next reply other threads:[~2018-05-25 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 20:59 sergiodj+buildbot [this message]
2018-05-25 21:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-26 20:07 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-05-30 21:14 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2018-06-03 2:16 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-06-03 2:20 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-06-03 2:39 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2018-06-07 2:40 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-09-13 14:32 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-09-13 14:50 ` 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=da505cff6e29b18244dc9f6886bcb4d436263dee@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).