cudawarped

> I found a way to check the cuda.h without install it, just use 7-Zip to open the cuda_12.4.1_551.78_windows.exe and find this directory cuda_12.4.1_551.78_windows.exe\cuda_cudart\cudart\include\cuda.h and found the macro denfination Whilst...

@opencv-alalek this resolves the issue mentioned but still results in build errors because `cudaarithm` uses `cudev` ( https://github.com/opencv/opencv_contrib/issues/3690). I suggest this is revisited when `cudev` can be built against CUDA...

> I still have an issue #3728 @jiapei100 Your issue is related to `cudev` (https://github.com/opencv/opencv_contrib/issues/3690) not `cudaarithm`.

> so the opencv don't supports the CUDA 12 well. It is actually as a issue. It doesn't currently support CUDA 12.4 when this change was made. This is in...

> I assume that the Python API calls some default allocator and does not use the CUDA pointer. This might be an issue that could be caused by > >...

Can this be closed as https://github.com/opencv/opencv/pull/23371 has now been merged. If anyone has the latest version of CUDA (12.1) and cuDNN (8.9.1) installed they can test this change with pre-built...

> So if we want to point users to this new capability the requirement will be to use OpenCV>=4.8? That's an interesting question, if this wasn't part of the contrib...

Not all of the CPU function has been implemented including [`setSpeckleRange()`](https://github.com/opencv/opencv_contrib/blob/b42682b4d151508af4729c8a5ef7da336e8fa525/modules/cudastereo/src/stereosgm.cpp#L56).

> Is it really an issue? Actually its a combination of two issues 1) an inability to search https://github.com/search?q=repo%3Aopencv%2Fopencv_contrib+blockReduce%3CBLOCK_SIZE&type=issues and 2) an existing issue (https://github.com/opencv/opencv_contrib/issues/3690)

> @cudawarped > > Is this working with **CUDA-12.3** ? Yes everything works with CUDA 12.3 and cuDNN 8.9.7.