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 cleanups from link_callbacks_einfo Date: Sat, 04 Nov 2017 17:45:00 -0000 [thread overview] Message-ID: <20dcd8cae7d87910f6c3936bad72e78b647a8de6@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 20dcd8cae7d87910f6c3936bad72e78b647a8de6 *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: 20dcd8cae7d87910f6c3936bad72e78b647a8de6 Remove cleanups from link_callbacks_einfo This removes a cleanup from link_callbacks_einfo by using std::string. gdb/ChangeLog 2017-11-04 Tom Tromey <tom@tromey.com> * compile/compile-object-load.c (link_callbacks_einfo): Use std::string.
next reply other threads:[~2017-11-04 17:45 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-04 17:45 sergiodj+buildbot [this message] 2017-11-04 17:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-11-04 18:13 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-11-04 18:38 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-11-04 18:42 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-11-04 18:50 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-11-04 18:56 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-11-04 19:00 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-11-04 19:04 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-11-04 19:05 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-11-04 19:12 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-11-04 19:19 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-11-04 19:31 ` 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=20dcd8cae7d87910f6c3936bad72e78b647a8de6@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).