fence.i Instruction
ConceptThe fence.i instruction is identified in the evidence as a RISC-V instruction used to synchronise instruction and data streams. In RISC-V verification, mishandling of fence.i is cited as one class of issue exposed by constrained-random stimulus generated with STING.
First seen 5/26/2026
Last seen 5/26/2026
Evidence 1 chunks
Wiki v1
WIKI
Overview
The fence.i instruction is a RISC-V instruction used to synchronise instruction and data streams.[C1]
Verification relevance
NEIGHBORHOOD
No graph connections found for this entity yet. It may appear in future ingestion runs.
explore full graph →RELATIONSHIPS
2 connectionsSTING has exposed mishandling of the fence.i instruction in practice.
fence.i is a RISC-V ISA instruction used to synchronise instruction and data streams.
LINKED ENTITIES
3 linksRISC-V instruction_set_context The evidence explicitly describes fence.i as a RISC-V instruction.
STING verification_tool_exposes_issues The evidence states that STING constrained-random stimulus exposed issues including mishandling of the fence.i instruction.
constrained-random test generation verification_method_context The evidence discusses constrained-random testing with STING and cites fence.i mishandling as an issue uncovered in that context.
CITATIONS
4 sources4 citations — click to collapse
[1] The fence.i instruction is used in RISC-V to synchronise instruction and data streams. # **Introduction**
[3] STING is described as a bare-metal, software-driven RISC-V generator producing C++-based random streams and ASM-style directed tests. # **Introduction**
[4] The evidence presents random stimulus and directed suites as complementary approaches in RISC-V verification. # **Introduction**