anematode

9 ms·

151.
by anematode 8mo ago
Awesome stuff! Does Go have profile-guided optimization? I'm wondering whether a profile could hint to the compiler how large to make the pre-reserved stack space.
152.
by anematode 8mo ago
If you're not doing recursion, I prefer using an appropriately sized thread_local buffer in this scenario. Saves you the allocation and does the bookkeeping of having one per thread
153.
Vulnerabilities in Cloudflare's vinext disclosed by Vercel(twitter.com)
2 points by anematode 8mo ago|0 comments
154.
by anematode 8mo ago
When push comes to shove, cheapness and hype can shove.
155.
by anematode 8mo ago
I've sometimes taken to using spaced en dashes, which I haven't seen in many AI comments: https://anemato.de/blog/emdash
156.
by anematode 8mo ago
Of course. I'm referring to rewrites of other software; you can easily launder GPLed code this way, for example.
157.
by anematode 8mo ago
Source code is one thing; tests covering the codebase are another. And if you just copy the source code or translate it one-to-one into a new language, rather than make a behavioral copy, there will be copyright issues.
158.
by anematode 8mo ago
> The better you document your work, the stronger contracts you define, the easier it is for someone to clone your work. Well said; this is my thinking as well. One person or organization can do the hard work of testing multiple approach
159.
by anematode 8mo ago
"El Palo Alto" As an example of how bogus this is: ... ensuring its projected lifespan extends at least 300 more years Not found in the given source and I have no clue where this came from. By the mid-1990s, diagnos
160.
by anematode 8mo ago
Maybe, but I think the OP is submitting this in bad faith (or got utterly bamboozled by the AI). I tried with recent clang and the specified flags, and the behavior is the same. (I think it's unlikely that it can be straight-up optimiz
161.
by anematode 8mo ago
It's slop: the numbers are fabricated. gcc -O3 -march=native -flto -DNDEBUG src/*.c -I include -o dmmsy_bench -lm ./a.out =========================================================================== n
162.
by anematode 8mo ago
Grokipedia is worse than useless. I scanned through an article on a semi-obscure topic which I know quite deeply, because I researched and wrote the Wikipedia article on that topic. There were dozens of factual errors, of course, but the fu
163.
by anematode 8mo ago
Unfortunate; I was hoping for some actual insights. Meanwhile, skipping to a random section, there's plainly false statements like > These instructions [pabsb, pabsw, ...] were added without changing the Core microarchitecture. They
164.
by anematode 8mo ago
Narrow indeed. If the function is small enough for the i-cache pressure to not matter, it's probably going to get inlined and the condition gets optimized out anyway. If it's big enough, then it's unclear, but microbenchmarks
165.
by anematode 8mo ago
The cardinal question: is the benefit of removing that branch worth the increase in i-cache footprint? I think it depends quite a bit... but also, the speed increases IME from doing this kind of thing can result not merely from the branch r
166.
by anematode 8mo ago
Well, yes and no. For example, coverage-guided fuzzers won't reliably find the taken branch in if (hash(x) == 0x12345678) { } Of course this is contrived, but you can imagine something similar where it requires a delicate set
167.
by anematode 8mo ago
Right? The cited use case is undefined behavior. Actually I can't think of a single realistic use case for this; despite the constant trumpeting of C++ folks on how constexpr will save C++, constant expressions are just too limited for
168.
by anematode 8mo ago
Dear lord, do we need an LLMs.txt for HN comments?
169.
by anematode 8mo ago
Not sure about that one. Fuzzers have a hard time creating certain narrow preconditions that a manual review can find.
170.
by anematode 8mo ago
Another common LLMism is elegant variation, i.e., avoiding repetition of words by using synonyms. (I assume they're RLed to do this religiously.) Of course, human writers do this too, but not nearly to the same extent in my experience.
171.
by anematode 8mo ago
Random pet peeve... it annoys me when people have old browser-specific aliases to standardized CSS properties. For example, -o-tab-size and -moz-tab-size instead of just tab-size. Those properties haven't done anything on Opera/Fi
172.
by anematode 8mo ago
> 100% of today’s SWE tasks are done by the models. Meanwhile, Claude Code is implemented using a React-like framework and has 6000 open issues, many of which are utterly trivial to fix.
173.
by anematode 8mo ago
Maybe it was just an oversight in the merge process? e.g. the diff was applied only to the RC and not to the release branch? idk
174.
by anematode 8mo ago
It found a small but nice little optimization in Stockfish: https://github.com/official-stockfish/Stockfish/pull/6613 Previous models including Claude Opus 4.6 have generally produced a lot of noise/thin
175.
by anematode 8mo ago
I'm trying to track down a GCC miscompilation right now ;)
176.
by anematode 8mo ago
Impressive, my sarcasm/bait detector almost failed me.
177.
by anematode 8mo ago
A simple C89 compiler is a textbook task; a GCC-compatible compiler targeting multiple architectures that can pass 99% of the GCC torture test suite is absolutely not.
178.
by anematode 8mo ago
Honestly, probably not a lot. Not that many C compilers are compatible with all of GCC's weird features, and the ones that are, I don't think are written in Rust. Hell, even clang couldn't compile the Linux kernel until ~10 y
179.
by anematode 8mo ago
Binary is wayyy less information dense than normal code, so it wouldn't work well at all.
180.
by anematode 8mo ago
Nah, it was at like 5500 before.

More ›