Revision 88a494316f004fc7121b45a052f6255fca9dce0b authored by Ulrich Pegelow on 17 March 2015, 20:52:30 UTC, committed by Pascal de Bruijn on 18 March 2015, 17:01:26 UTC
when darktable sees an new config file or if the OpenCL setup (GPUs) has changed we do a simple benchmarking test. If the fastest GPU is not clearly ahead of the CPU we de-activate OpenCL. user can always activate it again in the preferences dialog. rationale: avoid that a slow GPU negatively affects experience of users who are unaware of that fact. (cherry picked from commit ffe96c68aab08ebb90fb2106e330b2cd9e1abafb)
1 parent 44f2b8d
File | Mode | Size |
---|---|---|
cmake | ||
data | ||
doc | ||
packaging | ||
po | ||
src | ||
tools | ||
.clang-format | -rw-r--r-- | 1.5 KB |
.dir-locals.el | -rw-r--r-- | 94 bytes |
.gitignore | -rw-r--r-- | 125 bytes |
CMakeLists.txt | -rw-r--r-- | 11.3 KB |
README.md | -rw-r--r-- | 2.3 KB |
RELEASE_NOTES | -rw-r--r-- | 7.2 KB |
build.sh | -rwxr-xr-x | 5.1 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...