Update to build with CUDA 11.7.

[bdice]

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.

Rebuilding to allow __cuda pinning to match the recently released CUDA 11.7. I also added myself to the recipe maintainers, if that's alright with you @prashantkhoje!

cc: @quasiben @gmarkall

[conda-forge-linter]

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.

[bdice]

@conda-forge-admin, please rerender

[bdice]

@conda-forge-admin, please rerender

[gmarkall]

We'd talked before about removing the upper bound on the __cuda runtime constraint here:

ptxcompiler-feedstock/recipe/meta.yaml

Line 36 in a2ff337

- __cuda >={{ cuda_major ~ ".0" }},<={{ cuda_compiler_version }}

Does that need doing for this PR too?

[prashantkhoje]

If builds with 11.x can run in any 11.x environment, i agree we can remove upper bound.

I wonder why the build failed to run for ppc64le python 3.9.

[bdice]

We'd talked before about removing the upper bound on the __cuda runtime constraint here:

ptxcompiler-feedstock/recipe/meta.yaml

Line 36 in a2ff337

- __cuda >={{ cuda_major ~ ".0" }},<={{ cuda_compiler_version }}

Does that need doing for this PR too?

I wasn't 100% sure if you wanted to do that or not. I will remove it.

[prashantkhoje]

Thank you for the contribution.

[jakirkham]

Thanks Prashant! 🙏

[bdice]

Yes, thank you!