You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We made the decission to make all functions (that do not access pointers) constexpr. We want to check how much can this benefit execution time performance, if we do runtime compilation, and some of the variables are set as litterals in the runtime-compiled code.
Compare doing so vs not doing so.
We don't need to have the runtime compilation in order to test that, we can do it with current code base, to compare both cases.
Another idea that comes out from this, is that maybe we could reduce the amount of template parameters in the Ops, and make the runtime parameters "compile time" evaluated whe using rintime compilation, thanks to the constexpr lable on Ops and cxp functions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We made the decission to make all functions (that do not access pointers) constexpr. We want to check how much can this benefit execution time performance, if we do runtime compilation, and some of the variables are set as litterals in the runtime-compiled code.
Compare doing so vs not doing so.
We don't need to have the runtime compilation in order to test that, we can do it with current code base, to compare both cases.
Another idea that comes out from this, is that maybe we could reduce the amount of template parameters in the Ops, and make the runtime parameters "compile time" evaluated whe using rintime compilation, thanks to the constexpr lable on Ops and cxp functions.
Beta Was this translation helpful? Give feedback.
All reactions