You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In RV32, writes to tohost could be interpreted in more than a single way depending on when HTIF tick happens.
This was reported earlier #69 and was 'fixed' in 848312c.
However, I am not sure that this fix is factually correct, as according to this comment riscv-software-src/riscv-isa-sim#364 (comment) , blocking device character is not be supported in RV32 and only syscalls are supported.
The text was updated successfully, but these errors were encountered:
abukharmeh
changed the title
HTIF does not match pseudo specs and other implementation
HTIF does not match pseudo spec and other implementation
Feb 1, 2022
abukharmeh
changed the title
HTIF does not match pseudo spec and other implementation
HTIF does not match pseudo spec and other implementations
Feb 1, 2022
In RV32, writes to tohost could be interpreted in more than a single way depending on when HTIF tick happens.
This was reported earlier #69 and was 'fixed' in 848312c.
However, I am not sure that this fix is factually correct, as according to this comment riscv-software-src/riscv-isa-sim#364 (comment) , blocking device character is not be supported in RV32 and only syscalls are supported.
This claim is supported by this snippet in PK https://github.com/riscv-software-src/riscv-pk/blob/2f3e6f530384b4ab9f8b39bceb8e86f2ba51a835/machine/htif.c#L92-L107
The text was updated successfully, but these errors were encountered: