gerbin.blogg.se - Darktable for windows 10

The NEO initiative appears to have good momentum and is also based right here on github.

Intel IGA performance and driver quality moved forward considerably with Skylake.

NEO is both shorthand for "Intel Compute Runtime" and the name of the Intel development initiative.

There are as-is guards implemented in dt to defend against egregious implementation issues for instance a sanity-check at startup to ensure offload to GPU is actually faster than CPU.Īs discussed above, beignet and pocl are not considered fit for this purpose.

NEO support is at 2.1 at the time of writing and it is assumed 1.2 shall remain supported.

The two libraries blacklisted in current master, "beignet" and "pocl" shall remain blacklisted.

Specific cases TBC, but there is a darktable-cltest available. I will maintain a testing summary in a Wiki page on my fork. The target driver for this issue is Intel Compute Runtime.

Implement any additional blacklist/whitelist logic requiredĮdit to include Intel on Windows (and indeed Windows!) (suggestion by tests were not targeted for a Windows environment so there is platform support work required.īuild a consensus on what is supportable (I am happy to own support triage) The same principle can be used to compare CPU and GPU output. Thanks already to repurposing module integration/regression tests po/integration-tests #4818.

Volunteers to test various use cases with this build - see below. The exact build will depend on when I last rebased my branches. The "recent master" binary v0.1.0-exp%2Bgc6e676570 will be rebuilt from time to time, but with no formal version control. The 3.0.2 equivalent build: v0.1.0-exp%2Bg905d25d6d is intended to be identical to release except for the de-blacklisting of Neo. Make a Windows build from current master available for this testing purpose. (Note: author has no professional connection with Intel!)įollowing a review of the historical reasons for blacklisting (see summary below) it has been proposed that whitelisting recent versions of the Intel libraries and a selection of Intel chipsets from Gen 6/Kaby Lake onwards is sensible. However, it is believed that the original reasons for the blacklisting have been mitigated either through fixes in darktable (notably, issues with cache invalidation) or through the improving quality of Intel's libraries, support, and silicon in the domain.

OpenCL support for Intel chipsets is blacklisted in dt version 3.0.2. Is your feature request related to a problem? Please describe.