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: Allow instruction require more than one extension Date: Fri, 31 Aug 2018 16:33:00 -0000 [thread overview] Message-ID: <43135d3b15ce10a786704f9bb4736d834d6581a8@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 43135d3b15ce10a786704f9bb4736d834d6581a8 *** Author: Jim Wilson <jimw@sifive.com> Branch: master Commit: 43135d3b15ce10a786704f9bb4736d834d6581a8 RISC-V: Allow instruction require more than one extension 2018-08-29 Kito Cheng <kito@andestech.com> gas/ * config/tc-riscv.c (riscv_subset_supports): New argument: xlen_required. (riscv_multi_subset_supports): New function, able to check more than one extension. (riscv_ip): Use riscv_multi_subset_supports instead of riscv_subset_supports. (riscv_set_arch): Update call-site for riscv_subset_supports. (riscv_after_parse_args): Likewise. include/ *opcode/riscv.h (MAX_SUBSET_NUM): New. (riscv_opcode): Add xlen_requirement field and change type of subset. opcodes/ * riscv-dis.c (riscv_disassemble_insn): Check XLEN by riscv_opcode.xlen_requirement. * riscv-opc.c (riscv_opcodes): Update for struct change.
next reply other threads:[~2018-08-30 20:28 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-31 16:33 sergiodj+buildbot [this message] 2018-08-31 16:32 ` *** COMPILATION FAILED *** Failures on RHEL-s390x-m64, branch master *** BREAKAGE *** sergiodj+buildbot 2018-08-31 16:39 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-08-31 16:51 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-08-31 16:57 ` *** COMPILATION FAILED *** Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-08-31 17:08 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2018-08-31 17:38 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-08-31 17:52 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-08-31 17:53 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-08-31 17:53 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-08-31 17:53 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-08-31 17:54 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-08-31 17:54 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-09-09 7:18 ` Failures on Fedora-s390x-m64, " 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=43135d3b15ce10a786704f9bb4736d834d6581a8@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).