Troels Henriksen

My understanding is that the warning is completely insensitive to `CABAL_CONFIG`, so while the two files it talks about do exist, the message is misleading (none of them are used)....

Alternatively, the invocation of `warnOnTwoConfigs` could be moved into `getConfigFilePathAndSource` and only used in the `Default` case.

We can just check if `CABAL_DIR` is set before emitting the warning. It will be very ad hoc, but so is everything about the cabal config anyway.

Ugh, `getConfigFilePathAndSource` does not have access to the `Verbosity`.

Yeah, working on it.

Slicing with a tuple of a particular type, which encodes an LMAD, is a very interesting idea.

oclgrind is slated to be removed from Nixpkgs: https://github.com/NixOS/nixpkgs/pull/440273 I'd take a stab at upgrading oclgrind myself, but I am unfamiliar with LLVM's API, and it sounds like the problem...

Thank you for your continued maintenance of oclgrind! I assume that it is no longer an important part of your own toolbox, but there is definitely research I would *never*...