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] RISC-V: Fix disassembly of c.addi4spn, c.addi16sp, c.lui when imm=0 Date: Fri, 27 Oct 2017 03:57:00 -0000 [thread overview] Message-ID: <63a25ea0de6d2f6d45b26af8d9c808aa35962256@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 63a25ea0de6d2f6d45b26af8d9c808aa35962256 *** Author: Andrew Waterman <andrew@sifive.com> Branch: master Commit: 63a25ea0de6d2f6d45b26af8d9c808aa35962256 RISC-V: Fix disassembly of c.addi4spn, c.addi16sp, c.lui when imm=0 These are all invalid instructions, so they should not disassemble. opcodes/ChangeLog 2017-10-24 Andrew Waterman <andrew@sifive.com> * riscv-opc.c (match_c_addi16sp) : New function. (match_c_addi4spn): New function. (match_c_lui): Don't allow 0-immediate encodings. (riscv_opcodes) <addi>: Use the above functions. <add>: Likewise. <c.addi4spn>: Likewise. <c.addi16sp>: Likewise. gas/ChangeLog 2017-10-24 Andrew Waterman <andrew@sifive.com> * testsuite/gas/riscv/c-addi16sp-fail.d: New test. testsuite/gas/riscv/c-addi16sp-fail.l: Likewise. testsuite/gas/riscv/c-addi16sp-fail.s: Likewise. testsuite/gas/riscv/c-addi4spn-fail.d: Likewise. testsuite/gas/riscv/c-addi4spn-fail.l: Likewise. testsuite/gas/riscv/c-addi4spn-fail.s: Likewise. testsuite/gas/riscv/riscv.exp: Add new tests.
next reply other threads:[~2017-10-27 3:57 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-27 3:57 sergiodj+buildbot [this message] 2017-10-27 3:57 ` Failures on Ubuntu-AArch64-m64, branch master sergiodj+buildbot 2017-10-27 11:00 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-10-27 11:38 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-10-27 11:51 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-10-27 12:07 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-27 12:14 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-10-27 12:18 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-10-27 12:31 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-10-27 12:33 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-10-27 12:46 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-10-27 13:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-27 13:05 ` Failures on Fedora-x86_64-cc-with-index, " 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=63a25ea0de6d2f6d45b26af8d9c808aa35962256@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).