Viewing profile — znwu
znwu
HN member- Joined
- Wed, Oct 13, 2021, 1:41 AM UTC
- HN karma
- 30
- Public activity
- 40 items
- HN profile
- View on Hacker News ↗
About znwu
No profile information was provided.
Recent public activity
-
comment
Comment #35661801
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 sayi…
-
comment
Comment #35298842
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 …
-
comment
Comment #34349634
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 ho…
-
comment
Comment #33996186
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…
-
comment
Comment #33617972
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 generat…
-
comment
Comment #33494930
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…
-
comment
Comment #33426239
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 instruction…
-
comment
Comment #33396692
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 promi…
-
comment
Comment #33221008
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 dev…
-
comment
Comment #33138097
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.
-
comment
Comment #33076408
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 est…
-
comment
Comment #32958247
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 i…
-
comment
Comment #32929904
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.
-
comment
Comment #32874254
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. C…
-
comment
Comment #32640446
Hasn't looked into this. But definitely curious about the relationship between the two https://news.ycombinator.com/item?id=29217829
-
comment
Comment #32216714
Alongside with Windows long since 1.35 https://github.com/rust-lang/rust/pull/20367
-
comment
Comment #31971776
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 …
-
comment
Comment #31939702
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.
-
comment
Comment #31033667
This sounds suspiciously like using risc-v for web-assembly businesses. Any advantage for this method vs non-JIT wasm? (perfromance or platform compatibility?)
-
comment
Comment #31021185
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 rati…
-
comment
Comment #30788138
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];…
-
comment
Comment #30782731
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…
-
comment
Comment #30748997
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 ove…
-
comment
Comment #30719807
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 …
-
comment
Comment #30719750
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 dep…