Basically all C++ libraries define a FORCEINLINE macro and sprinkle it everywhere, across all compilers. I wonder how much that is really verified to be helpful.
-
I had issues at scale with that in debug, trivial getters showing up in my profiles. Had massive improvments after forceline. Then again I'm the crazy type that profiles and optimizes debug builds :P
Ever considered solutions where certain libraries are compiled in debug and others are with optimization? Gameplay programmers, for instance, can let the graphics and physics library be optimized while their own code is in debug. Done this before and it proved useful.
-
-
Yeh, that's a common approach, and I do that for thirdparty libs but I like to have the entire engine in debug, else people get lazy and it becomes death by a 1000 cuts. I've never seen a fast debug build be slow in release ;)
-
I'm generally the same way. If your debug build is 30fps it's likely your release will hit 60. Great way of hitting your target performance marks.
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.