Commit graph

58 commits

Author SHA1 Message Date
Austin Roach
688ed5e00d RISC-V j/jr semantics: use goto instead of call
In the RISC-V binaries that I've been looking at, the j and jr
instructions have been used exclusively for intraprocedural control flow
transfers, where the function-call hinting associated with the CALL
p-code op leads to nasty side effects in the control flow
reconstruction.
2020-07-20 20:48:37 -04:00
ghidorahrex
b7481d2088 Merge remote-tracking branch
'origin/GT-3524_ghidorahrex_PR-1450_mumbel_riscpatt'

Fixes #1450
2020-07-16 14:09:41 -04:00
ghidra1
3c99e1063c Corrected RISCV language files which need blank line at end 2020-02-20 14:17:31 -05:00
ghidorahrex
9faf39baed Fixed sleighCompiler test failures with riscv. 2020-02-18 14:43:18 -05:00
ghidorahrex
67631a27ef GT-3524: Certifying riscv pattern files. 2020-02-06 10:40:40 -05:00
mumbel
5fc98745bc initial patterns 2020-01-12 19:16:18 -06:00
ghidorahrex
b628a7e46f GT-3389: Certifying RISCV processor module. 2019-12-10 15:22:25 -05:00
mumbel
d7e51ee515 RISC-V processor
[riscv] Added context register for extensions

[riscv] missed a define in refactor

[riscv] got 100% on RV32IMC

[riscv] Add throw away script to generate SLEIGH

[riscv]

Fixes from SleighDevTools

- R4-type were using a bad bit pattern that broke the rs3 operand
- mul had a copy/paste typo that ignored the rs2 operand
- bad define guard for compressesed instruction
2019-12-10 14:04:05 -06:00