Hao

Results 12 issues of Hao

### Before start - [X] I have read the [RISC-V ISA Manual](https://github.com/riscv/riscv-isa-manual) and this is not a RISC-V ISA question. 我已经阅读过 RISC-V 指令集手册,这不是一个指令集本身的问题。 - [X] I have read the [XiangShan...

bug report

Add `riscv64-unknown-elf-` as `CPT_CROSS_COMPILE` when `riscv64-unknown-linux-gnu-` does not exist.

According to the privileged [specification](https://riscv.org/technical/specifications/) in chapter **3.1.9. Machine Interrupt Registers**, some bits in MIE are set to zero. ![image](https://github.com/user-attachments/assets/82ba2a05-6a2e-40fe-99af-8a45b955439e) However, if we write `0xffffffff` to `mie`, the NEMU will...

### Before start - [x] I have read the [RISC-V ISA Manual](https://github.com/riscv/riscv-isa-manual) and this is not a RISC-V ISA question. 我已经阅读过 RISC-V 指令集手册,这不是一个指令集本身的问题。 - [x] I have read the [XiangShan...

bug report

I have tested it in **the newest version**, it works! No more `mstatus` different for now. However, this test case raise `mcause` different: ``` sh s2, 1259(s0) # test case...

### Before start - [x] I have read the [RISC-V ISA Manual](https://github.com/riscv/riscv-isa-manual) and this is not a RISC-V ISA question. 我已经阅读过 RISC-V 指令集手册,这不是一个指令集本身的问题。 - [x] I have read the [XiangShan...

not bug

I installed the co-simulation system, followed this [tutorial](https://ibex-core.readthedocs.io/en/latest/03_reference/cosim.html#setup-and-usage) to install cosim and tested it on ibex. One of the test cases shows unexpected behavior: ``` FAILURE: Co-simulation mismatch at time...

Type:Question

## Observed Behavior When write 0x01 to `mseccfg`(0x747), some unknown behavior happened: ibex jump to `_vectors_start`. I have tested some values, when we write 0x4 or 0x8, ibex is normal,...

Type:Bug

Our fuzzing methodology uncovered anomalous behavior in the Rocket [f517abb](https://github.com/chipsalliance/rocket-chip/commit/f517abb), using Spike as the reference model. **Test Case Description:** At `pc = 0x80000054,` the `mepc` is `0x8000005e`, which corresponds to...

Our fuzzing methodology uncovered anomalous behavior in the BOOM v3 processor, using Spike as the reference model. **Test Case Description**: At `pc = 0x80000054`, the `mepc` is `0x8000005e,` which corresponds...