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.
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).
-
-
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.
-
We had this on one of the engines I worked on, a per frame linear buffer that would reset at a known time. It was shared among threads though, and it would be double buffered so GPU could access it on a different frame as well.
- Show replies
New conversation -
-
-
It works just as well in non-game software. I have this solution in-place in our current software that has no concept of a “frame”. Each “work item” gets a temp allocator.
-
Meant “server software” more specifically than non-game.
End of conversation
New conversation -
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.