[FEA] Provide cuOpt builds with CUOPT_INSTANTIATE_INT64 enabled
@tmckayus is already working on this.
Since Mar 11, 2026.
- Dominant language
- Cuda
- Stars
- 1k
- Forks
- 233
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 95
Description
In order to make the GAMS<->cuOpt link (see also) work with very large problems with more than 2^31 non-zeroes (which GAMS supports with other solvers like, for example, CPLEX already), it would be helpful to have a prebuilt cuOpt package available from pip that has CUOPT_INSTANTIATE_INT64=1. I attempted to build it myself in a fork and that sort of worked and produced a wheel but I struggle to integrate this into the link.
Hence I would be interested in some instructions for specifically building cuOpt with int64 and using that in conjunction with the most recent nightly build wheels OR even better have int64-enabled packages directly available in the NVIDIA repositories. I understand making INT64 the default doesn't make sense as it would blow up the memory footprint (and hence slow down processing) even when INT32 is perfectly fine (for smaller problems).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.