Revise riscv-arch-test description and Makefile

Author: xiaohan484

.gitignore

@@ -1,6 +1,6 @@
 build/DOOM1.WAD*
 shareware_doom_iwad.zip*
 build/rv32emu
-build/compliance
+build/arch-test
 *.o
 *.o.d

.gitmodules

@@ -1,3 +1,3 @@
 [submodule "riscv-arch-test"]
 	path = riscv-arch-test
-	url = https://github.com/riscv-non-isa/riscv-arch-test.git
+	url = https://github.com/riscv-non-isa/riscv-arch-test

Makefile

@@ -81,20 +81,20 @@ check: $(BIN)
 	(cd $(OUT); ../$(BIN) hello.elf)
 	(cd $(OUT); ../$(BIN) puzzle.elf)
 
-COMPLIANCE_DIR ?= ./riscv-arch-test 
-export RISCV_TARGET = compliance-target
-export RISCV_PREFIX = riscv-none-embed-
+ARCH_TEST_DIR ?= ./riscv-arch-test 
+export RISCV_TARGET = arch-test-target
+export RISCV_PREFIX ?= riscv-none-embed-
 export TARGETDIR = $(shell pwd)
 export XLEN = 32
 export JOBS ?= -j
-export WORK = $(TARGETDIR)/build/compliance
+export WORK = $(TARGETDIR)/build/arch-test
 
-$(COMPLIANCE_DIR):
+$(ARCH_TEST__DIR):
 	git submodule update --init
 
-compliance: $(BIN) $(COMPLIANCE_DIR)
-	$(Q)$(MAKE) --quiet -C $(COMPLIANCE_DIR) clean;
-	$(Q)$(MAKE) --quiet -C $(COMPLIANCE_DIR);
+arch-test: $(BIN) $(ARCH_TEST__DIR)
+	$(Q)$(MAKE) --quiet -C $(ARCH_TEST_DIR) clean
+	$(Q)$(MAKE) --quiet -C $(ARCH_TEST_DIR)
 
 demo: $(BIN) $(OUT)/DOOM1.WAD
 	(cd $(OUT); ../$(BIN) doom.elf)

README.md

@@ -30,21 +30,31 @@ make demo
 The build script will then download data file for Doom automatically. SDL2 based window
 should appear when Doom is loaded and executed.
 
-## Run riscv-arch-test
+## riscv-arch-test
 
-Once the submodule `riscv-arch-test` is pulled, run all the available compliance test via command:
+The RISC-V Architectural Tests, [riscv-arch-test](https://github.com/riscv-non-isa/riscv-arch-test) is basic set of tests that ensure software implemented can be match important aspects of the RISC-V specification.(not a **substitute for rigorous design verification**)
+
+There has the **reference signatures** generate by [RISC-V SAIL](https://github.com/riscv/sail-riscv) and the test signatures, specific memory location can be written.Once the test be executed, the **test signatures** will be written by testing-model(rv32emu-next)during the test, and it will be compared to **reference signature**.The test will pass if both signatures exactly match.
+
+[riscv-arch-test](https://github.com/riscv-non-isa/riscv-arch-test) is integrated with submodule, and the setup was done.Once the submodule `riscv-arch-test` is pulled, run all the available riscv-arch-test via command:
 ```shell
-make compliance
+make arch-test
 ```
 
 * To run the tests for specific extension, set the environmental variable `RISCV_DEVICE` to one of `I`,`M`,`C`,`Zifencei`,`privilege`.
 ```shell
-make compliance RISCV_DEVICE=I
+make arch-test RISCV_DEVICE=I
 ```
 * To run a specific test case,set both `RISCV_DEVICE` and `RISCV_TEST`.For example:
 ```shell
-make compliance RISCV_DEVICE=M RISCV_TEST=div-01
+make arch-test RISCV_DEVICE=M RISCV_TEST=div-01
 ```
+The detail in setup enviroment variables is in [RISC-V Architectural Testing Framework](https://github.com/riscv-non-isa/riscv-arch-test/blob/master/doc/README.adoc) **5.1 Setup environment variables**.
+
+Reference: 
+[riscv-arch-test repository](https://github.com/riscv-non-isa/riscv-arch-test)
+[RISC-V Architectural Testing Framework](https://github.com/riscv-non-isa/riscv-arch-test/blob/master/doc/README.adoc)
+[RISC-V Architecture Test Format Specification](https://github.com/riscv-non-isa/riscv-arch-test/blob/master/spec/TestFormatSpec.adoc)
 
 ## Customization
 

compliance-target/device/rv32i_m/C/Makefile.include renamed to arch-test-target/device/rv32i_m/C/Makefile.include

@@ -13,4 +13,3 @@ SECTIONS
   .bss : { *(.bss) }
   _end = .;
 }
-