Tim Hutt

Unspecified behaviour with explicit writes to minstret on RV32

4

On RV32 if `minstret` the lower 32 bits of `instret` is 0xFFFFFFFF, and `minstreth` (the upper 32 bits) is 0. And then you do ``` csrw minstret, zero ``` What...

Spec does not define "should"

1

Most formal specs I've read define words like "should", "must", "may", up front, but the RISC-V spec does not appear to. Despite that "should" appears dozens of times, often in...

Unimplemented PMPs

6

The spec says: > Up to 64 PMP entries are supported. Implementations may implement zero, 16, or 64 PMP entries; the lowest-numbered PMP entries must be implemented first. All PMP...

Add static typing

1

As far as I can tell this is missing static types or type stubs. The best way to do it is to add type hints into the code, then you...

I get this error: ``` Error: Too long output directory: `\\?\D:\lockfw\target\riscv32imac-esp-espidf\release\build\esp-idf-sys-eac617bcbe734de9\out`. Shorten your project path down to no more than 10 characters (or use WSL2 and its native Linux filesystem)....

The `constants.isa_regex` requires the sub-extensions (Z..., S...) to immediately follow the main extensions without a separating underscore. For example this is considered valid: RV32IMAFCSUZicsr_Zifencei_Zba_Zbb_Zbs But this is not: RV32IMAFCSU_Zicsr_Zifencei_Zba_Zbb_Zbs Both...

Add warning about extreme path length limit on Windows

5

This is a very surprising gotcha and kind of a pain to have to regenerate & recompile your project if you didn't know about it. Which you definitely didn't.

Plugin incompatible with built-in tsserver `enableProjectDiagnostics`

24

Edit: From https://github.com/denoland/vscode_deno/issues/437#issuecomment-930501333: > Finally figured it out. I have this in my VSCode settings: > > ``` > "typescript.tsserver.experimental.enableProjectDiagnostics": true > ``` > > Without that setting it works...

Fix bigIntToBuffer for numbers that start 0x9

6

Numbers that start 0x9... did not have '00' prepended. Fixes #163 Probably a good idea to add a unit test for this function! I don't have time at the moment...

OpenSSH private keys not decoded correctly

2

We have an OpenSSH key that was generated on MacOS. `ssh2-streams` unfortunately decodes it incorrectly: ``` const s = require("ssh2-streams"); const keys = s.utils.parseKey(`-----BEGIN OPENSSH PRIVATE KEY----- b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAABlwAAAAdzc2gtcn NhAAAAAwEAAQAAAYEA6oDCeE6kPkmq0SUpmBz7aojSWz9jow/fqcSPnXVfANNW3A9zNi57 ZvOPyR0PuFk93O0Ybrj5DRZRFhnFzSkY5Kq0D3FLjwxM4hCKtjz+fBjBJ8HaCRtpLQa4pX...