obl

14 ms·

151.
by obl 10y ago
Unless you want programmers to explicitely manage this fast memory the hardware is a better place to do those optimizations than the software. Compilers (even the high-end modern ones) are very quickly clueless about both memory and executi
152.
by obl 11y ago
as for the synchronization use case, even though it's probably way more expensive to invalidate another thread's instruction cache than any other usual sync. method, it can be useful if there is a huge number of synchronization po
153.
by obl 11y ago
I think the point was mostly to only let the bot have as much information as a player would get on the screen : no omniscient knowledge about the state of every visible unit on the map. You'd probably also want to rate limit the inputs
154.
by obl 11y ago
at first glance it seems to be missing a write barrier to catch new references from old gen to new gen, which is a very important part of any generational collector
155.
by obl 11y ago
The advantage of any checked memory management scheme, be it a runtime thing like a tracing gc or a fancy type system, is not to give a tighter over-approximation of liveness but to guarantee that you never under-approximate it. In other wo
156.
by obl 11y ago
This is wrong. The notion of predictability in modern branch predictors is much more sophisticated than simply "strongly taken"/"strongly not taken". i%2==0 is periodic of period 2. If I am to believe Agner, we&#x27
157.
by obl 11y ago
The big advantage in optimizing a trace at a time is that you don't have inbound control flow. In fact, the first transform that a tracing JIT does to the code (trace extraction) can be seen as removing every inbound CF edge except the