-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Fix wrong cache line size of riscv64 #145078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Confirmed by looking at all readily available implementations. @bors try jobs=dist-riscv64-linux |
This comment has been minimized.
This comment has been minimized.
Fix wrong cache line size of riscv64 try-job: dist-riscv64-linux
@bors r+ rollup=always |
+1 (no changes required) except that "wrong" in the title seems a bit misleading (so I'll leave a note here). The RISC-V architecture (itself) defines nothing about cache line size (in fact, we don't actually need cache in the minimal configuration). However, for baseline purposes, there's RISC-V Profiles specification1. Footnotes
|
Rollup of 6 pull requests Successful merges: - #142215 (Use -Zmir-opt-level=0 in tests for MIR building) - #143341 (Mention that casting to *const () is a way to roundtrip with from_raw_parts) - #145078 (Fix wrong cache line size of riscv64) - #145290 (Improve std::fs::read_dir docs) - #145335 (Move WTF-8 code from std into core and alloc) - #145904 (Move `riscv64-gc-unknown-linux-musl` from Tier 2 with Host tools to Tier 2) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of #145078 - minxuanz:riscv-cacheline, r=samueltardieu Fix wrong cache line size of riscv64 see https://go-review.googlesource.com/c/go/+/526659, All of riscv CPU using 64B for cache-line size.
see https://go-review.googlesource.com/c/go/+/526659, All of riscv CPU using 64B for cache-line size.