With 64 bit address spaces, thread stacks should have GBs reserved by default, and programming with alloca should be encouraged. A lot of string and container work could be done at high performance with alloca and no frees if you don't let them escape.
-
-
Replying to @ID_AA_Carmack
Having a per-thread temporary allocator that is a standard convention, so that everyone including libraries can use it, is better... you can return temporary strings / arrays / nodes from functions, etc. (I do this all the time in the language I am working on).
2 replies 1 retweet 72 likes -
Replying to @Jonathan_Blow @ID_AA_Carmack
You just pretend like you have a GC for all these things, and it just gets completely reset once per frame at a known point.
5 replies 0 retweets 50 likes -
Replying to @Jonathan_Blow @ID_AA_Carmack
So like objective c autorelease pool?
1 reply 0 retweets 0 likes
Replying to @EscJaeger @ID_AA_Carmack
No, because it does not have the same imposition of structure, not performance impact.
10:39 AM - 2 May 2021
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.