Travis Whitaker

Hardware access is going to be tricky; I don't even think there are AWS instances with access to this hardware available yet. I think as long as a foreign function...

It's true that Accelerate would need to treat kernels that use WMMA specially, since they operate at the warp-level. Foreign functions using WMMA wouldn't be executable on other backends, although...

Ah yup, that's what I was missing. I'm a bit surprised this was accepted, the resulting behavior seems quite confusing: - Integer decimal literals -> user sees confusing error on...

> `c-sources` and `asm-sources` are passed to GHC, which handles them for us, that makes supporting these "easy". Perhaps GHC itself should learn to handle RC files. > What one...

@phadej Do you have any thoughts on which approach might be better: - cabal treats `rc-sources` like `c-sources`, `asm-sources` etc., and GHC learns to handle passed in RC files (GHC...

@cocreature If you have no objections I'm going to proceed with this.

hsc2hs already supports cross compilation, it just doesn't support these constructs when run in cross compilation mode: - `#{const_str}` - `#{let}` - `#{def}` - Custom functions, like `hsc_inject` and `hsc_patsyn`...

Is there a downside to enabling it by default (even if there's no data-files field in a package)?

Suppose I'm responsible for developing package A, which depends on package B. I have an x86 machine but I'm deploying A to aarch64. I want to be able to cross-build...

To work around this, I just override every single plan in my spec to have `planned = true`, that seems to recover the old behavior.