Permit more CUDA versions

[mabraham]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[mabraham]

@conda-forge-admin please rerender

[mabraham]

Motivating discussion at #15 (comment)

[douglowe]

Looks like we need a build matrix to define which CUDA versions to build for - so we aren't trying to build for cuda 10.2 (and earlier).

[mabraham]

@conda-forge-admin please rerender

[mabraham]

@conda-forge-admin please rerender

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [50]

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jakirkham]

Regarding cicc this should be in $BUILD_PREFIX/nvvm/bin

Could you please share some more details on what is calling cicc (if known)?

From a cursory look at this recipe (and the upstream code), didn't see cicc, but that is more likely because I don't know where to look