Cache compiled OpenCL kernels at two locations - #22349
Merged
TurboGit merged 1 commit intoSep 21, 2026
Merged
Conversation
jenshannoschwalm
added
feature: enhancement
- We now use two directories for the cached kernels thus a fast mode toggle won't enforce a recompilation of all kernels. - We read the "opencl_fast" conf just once while initializing the OpenCL subsystem - For debugging and integration testing we always use the non-fast kernels.
jenshannoschwalm
force-pushed
the
split_opencl_fast_kernels
branch
from
September 21, 2026 11:11
8164082 to
d0f0b3d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:
We now use two directories for the cached kernels thus a fast mode toggle won't enforce a recompilation of all kernels.
We read the "opencl_fast" conf just once while initializing the OpenCL subsystem
For debugging and integration testing we always use the non-fast kernels.
I have read CONTRIBUTING.md and the coding style.
I have not merged master into the topic branch.
The pull request is one logical change, and every commit compiles on its own.
I ran the relevant tests: unit tests,
src/tests/integration/where the pixelpipe is touched, ordarktable-clias a headless smoke test.New user-visible strings use
_(), new preferences are registered indata/darktableconfig.xml.in.A
RELEASE_NOTES.mdentry was added (only needed if fixing an issue in a release). Do not reference GitHub issues.