znwu

6 ms·

1.
by znwu 3y ago
A bit of clickbait. Brief explanation of why that huge perf gap on a well-solved problem: 1. The `memcpy` idea is trivial. I know it's there to serve a different argument. But saying "professional" can't think of `memcpy
2.
by znwu 4y ago
This page has some interesting ideas about "safety" without any pre-conditions. As a starter, Java is safe. Probably safer than most of the C-based candidates on this list. And we are only speaking about Java without tooling vs C
3.
by znwu 4y ago
The open-sourced toolchain of RISC-V accepts any kind of extensions as long as they are in the reserved code space, basically out-of-the-box. The current ratifying body does not hold any special toolchain or legal influence other than its p
4.
by znwu 4y ago
My Gosh, what was happening with this project? At first they target to ship in chrome 97, then 101, then 105, then 109, now 113. Are we building fusion reactors that are constantly four months away?
5.
by znwu 4y ago
Well this is bad. Just checked the code, `RandomState` invokes `wasi::random_get()` on wasi target. It means virtually every std program in Rust would require random number generator privilege in the upcoming WASI unless the author intentio
6.
by znwu 4y ago
This article turned up with a valuable proposition. Although I would still argue open source software itself is as political as it can get (Forked code has no value. Communities of people behind the code matters), but I do agree that such t
7.
by znwu 4y ago
RISC no longer has the clear border as it had 30 years ago. Nowadays RISC just means an ISA has most of the following points: 1. Load/Store architecture 2. Fixed-length instructions or few length variations. 3. Highly uniform instructi
8.
by znwu 4y ago
Finally some updates after all these years. I'm just curious about the relations between the older "nanoprocess" and the now Component Model. Previously the nanoprocess model promised fine-grained containerization, I wonder i
9.
by znwu 4y ago
On ISA design, it is just so wrong to endorse the opinion of a single person. ISA design has three significant parties of interest: IC designers, compiler authors, and software developers. No one can master these three fields all at once. N
10.
by znwu 4y ago
Chip and ISA are almost irrelevant stuff. No matter how you emphasize on end product performance, you cannot deny there SHOULD be a metric to compare ISA designs.
11.
by znwu 4y ago
From my perspective, Rust does not belong in kernel. But meanwhile Linux kernel does not belong in modern infrastructure. Until the day a mature kernel-oriented language and an established kernel showed themselves, Frankenstein experiments
12.
by znwu 4y ago
They seem to adopt a rapid iteration model closer to browser rather than typical language runtimes. So a browser 1.0 is nothing close to finished. I personally have no problem on it. But I think it is indeed strange that they sound so serio
13.
by znwu 4y ago
Just curious, how would a high-level IR processor knows beforehand that a certain piece of code was longer/shorter than 4kB/1MB, if it do not try to compile it in pieces first.
14.
by znwu 4y ago
Mainly because they can. They already have excellent team & experience in designing low power cores from the ground up, and also they have their great LLVM team for the compiler. Core plus compiler, that's all you need for a in-hou
15.
by znwu 4y ago
Hasn't looked into this. But definitely curious about the relationship between the two https://news.ycombinator.com/item?id=29217829
16.
by znwu 4y ago
Alongside with Windows long since 1.35 https://github.com/rust-lang/rust/pull/20367
17.
by znwu 4y ago
For those who are wondering why the heck would a microarhitectural exploit would "work" on a ISA level as the title suggested: No, it doesn't. This paper talks only about textbook RISC-V BOOM cores. Interesting work, but
18.
by znwu 4y ago
I've been tracking this since May. I'd say it's disappointing that it did not make itself into 1.62 in the end.
19.
by znwu 4y ago
This sounds suspiciously like using risc-v for web-assembly businesses. Any advantage for this method vs non-JIT wasm? (perfromance or platform compatibility?)
20.
by znwu 4y ago
I would say the current state of RISC-V is complete but still lacks the final kick. Yes, you can now build an application core out of it, given that V, B, K extensions are now ratified under RVA22. However most high-performance u-archs are
21.
by znwu 5y ago
Then write up an actually meaningful array processing function and translate it into asm is even less rocket science. The author starts with a apparently meaningless `int x = a[i];`, but did not ask an obvious question before digging in: wh
22.
by znwu 5y ago
Yes it is negligible. The problem is that indexed load/store is a non-issue. There are ready-to-use simulation data that shows indexed load/store has minimal impact on dynamic code size.If someone uses an overkill feature to expla
23.
by znwu 5y ago
Yes, the author's defence for Myth #1 does not strike me as a correct defence from the RISC-V perspective. Going to compressed instruction and compressed macro-op fusion is way overkill for the very basic indexed load/store proble
24.
by znwu 5y ago
There is also the problem of binary layout. RPC values on binary size, and IPC values on latency with zero ser/des. The two binary layouts are simply incompatible. You can do zero copy with RPC, but that does not help with ser/des
25.
by znwu 5y ago
Sync and async are all about cooperatively yielding control flow. However, in many cases, you may want to yield control on IPC, or to hold onto control on RPC. Yielding control depends on the sender logic. IPC/RPC depends on receiver c
26.
by znwu 5y ago
> In the V-extension, they have an instruction named "vrgather". > But that instruction is not a gather load instruction. This instructoin is just a shuffle instruction. I think on the contrary, x86's permute/shuff
27.
by znwu 5y ago
Cool to hear it comes with concurrent mode support. Are there any other Rust UI toolkits that introduced concurrent mode? I would like to try out more of them in the future.
28.
by znwu 5y ago
I would personally describe memory safety as "all memory accesses to variables are guaranteed to yield a valid value under the type specified by the variable". So that immediately rules out buffer overflows, use-after-free, double
29.
by znwu 5y ago
RVA22 Profile: https://github.com/riscv/riscv-profiles/blob/main/profiles.a... Zba and Zbb are both mandatory extensions. Zbc, Zbkb, Zbkc, Zbkx are all supported extensions. Zba and Zbb contain most usef
30.
by znwu 5y ago
The problem is that, when people say "math" , they usually refer to HPC, or sometimes machine learning, or in very rare occasions, symbollic math. They usually don't mean arbitrary-precision math. In fact, I'm not aware

More ›