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] Change find_partial_die_in_comp_unit to dwarf2_cu::find_partial_die Date: Mon, 26 Feb 2018 17:35:00 -0000 [thread overview] Message-ID: <d590ff257c81d5aac51928148ce74b0131bbf81c@gdb-build> (raw) *** TEST RESULTS FOR COMMIT d590ff257c81d5aac51928148ce74b0131bbf81c *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: d590ff257c81d5aac51928148ce74b0131bbf81c Change find_partial_die_in_comp_unit to dwarf2_cu::find_partial_die This patch changes find_partial_die_in_comp_unit to a dwarf2_cu method find_partial_die. gdb: 2018-02-26 Yao Qi <yao.qi@linaro.org> * dwarf2read.c (struct dwarf2_cu) <find_partial_die>: New method. (find_partial_die_in_comp_unit): Change it to dwarf2_cu::find_partial_die. (find_partial_die): Update.
next reply other threads:[~2018-02-26 17:35 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-26 17:35 sergiodj+buildbot [this message] 2018-02-26 17:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2018-02-26 17:47 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-02-26 17:47 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-02-26 17:50 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-02-26 18:07 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-26 18:12 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-02-26 18:25 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-02-26 18:36 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-02-27 4:11 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-27 4:43 ` 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=d590ff257c81d5aac51928148ce74b0131bbf81c@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).