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: Add .insn support.
Date: Wed, 14 Mar 2018 23:20:00 -0000	[thread overview]
Message-ID: <0e35537d754f1c687850d1caccb2d78d2e418391@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 0e35537d754f1c687850d1caccb2d78d2e418391 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 0e35537d754f1c687850d1caccb2d78d2e418391

RISC-V: Add .insn support.

	gas/ChangeLog
	2018-03-07  Kito Cheng  <kito.cheng@gmail.com>
	* config/tc-riscv.c (opcode_name_list): New.
	(opcode_names_hash): Likewise.
	(init_opcode_names_hash): Likewise.
	(opcode_name_lookup): Likewise.
	(validate_riscv_insn): New argument length, and add new format
	which used in .insn directive.
	(md_begin): Refine hash table initialization logic into
	init_opcode_hash.
	(init_opcode_hash): New.
	(my_getOpcodeExpression): Parse opcode name for .insn.
	(riscv_ip): New argument hash, able to handle .insn directive.
	(s_riscv_insn): Handler for .insn directive.
	(riscv_pseudo_table): New entry for .insn.
	* doc/c-riscv.texi: Add documentation for .insn directive.
	* testsuite/gas/riscv/insn.d: Add testcase for .insn directive.
	* testsuite/gas/riscv/insn.s: Likewise.

	include/ChangeLog
	2018-03-07  Kito Cheng  <kito.cheng@gmail.com>
	* opcode/riscv.h (OP_MASK_FUNCT3): New.
	(OP_SH_FUNCT3): Likewise.
	(OP_MASK_FUNCT7): Likewise.
	(OP_SH_FUNCT7): Likewise.
	(OP_MASK_OP2): Likewise.
	(OP_SH_OP2): Likewise.
	(OP_MASK_CFUNCT4): Likewise.
	(OP_SH_CFUNCT4): Likewise.
	(OP_MASK_CFUNCT3): Likewise.
	(OP_SH_CFUNCT3): Likewise.
	(riscv_insn_types): Likewise.

	opcodes/ChangeLog
	2018-03-07  Kito Cheng  <kito.cheng@gmail.com>
	* riscv-opc.c (riscv_insn_types): New.


             reply	other threads:[~2018-03-14 23:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 23:20 sergiodj+buildbot [this message]
2018-03-14 23:20 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-03-14 23:32 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-15  0:01 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-03-15  0:16 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-03-15  0:25 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-03-15  0:26 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-03-15  0:29 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-03-15  0:31 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-03-15  0:32 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-03-15  0:42 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-03-15  0:53 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-03-15  0:55 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-03-15  0:58 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-03-15  1:32 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2018-03-15  2:46 ` Failures on Ubuntu-AArch64-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=0e35537d754f1c687850d1caccb2d78d2e418391@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: link
Be 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).