Optimize the null boundary check
All threads resolved!
All threads resolved!
From Mattermost discussion, it emerged that the "null" boundary check which doesn't check anything is actually used for something in production (while processing measurements), so let's optimize it into nothingness.
Merge request reports
Activity
Filter activity
changed milestone to %0.15.00
added Improvement label
added 31 commits
-
6f0b99d7...917eb8ff - 30 commits from branch
acts:master
- c69ee585 - Optimize the null boundary check
-
6f0b99d7...917eb8ff - 30 commits from branch
enabled an automatic merge when the pipeline for c69ee585 succeeds
added Approved label
added 3 commits
-
c69ee585...b5d57286 - 2 commits from branch
acts:master
- 41e3ae0c - Optimize the null boundary check
-
c69ee585...b5d57286 - 2 commits from branch
@pagessin This MR will need a re-approval as it was rebased on its freshly merged sibling.
- Resolved by Hadrien Benjamin Grasland
Choo choo! (Those OOM errors remind me that I still need to try out LLVM 9's -ftime-trace feature, as a possibly more ergonomic alternative to Templight)
Edited by Hadrien Benjamin Grasland
mentioned in commit a86eff5f
Please register or sign in to reply