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] Rewrite arm_record_coproc_data_proc and arm_record_data_proc_misc_ld_str Date: Thu, 01 Feb 2018 16:11:00 -0000 [thread overview] Message-ID: <2d9e6acbdbc528563a9df5445584a8a150a86527@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 2d9e6acbdbc528563a9df5445584a8a150a86527 *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: 2d9e6acbdbc528563a9df5445584a8a150a86527 Rewrite arm_record_coproc_data_proc and arm_record_data_proc_misc_ld_str When I triage some reverse debugging test fails on arm-linux, I find arm_record_coproc_data_proc and arm_record_data_proc_misc_ld_str is not friendly to instruction encoding on ARM ARM. This patch rewrites them, in a way match more closely to the manual. gdb: 2018-02-01 Yao Qi <yao.qi@linaro.org> * arm-tdep.c (arm_record_data_proc_misc_ld_str): Rewrite it. (arm_record_coproc_data_proc): Likewise.
next reply other threads:[~2018-02-01 16:11 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-01 16:11 sergiodj+buildbot [this message] 2018-02-01 16:11 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-02-01 16:23 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-02-01 16:30 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-02-01 16:38 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-02-01 16:44 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-02-01 16:47 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-02-01 16:58 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-02-01 17:06 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-01 17:10 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-02-01 17:21 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-02-01 17:24 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-02-01 18:40 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2018-02-01 20:03 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-01 20:36 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-02-01 21:08 ` Failures on Ubuntu-AArch32-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=2d9e6acbdbc528563a9df5445584a8a150a86527@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).