You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that when index_type in cuda::std::extents is unsigned int then dynamic extents are truncated to a smaller type. It works correctly if index_type is int, not sure about other types.
pciolkosz
changed the title
[BUG]: cudastd::extents::static_extent truncates cudastd::dynamic_extent when index_type is unsigned int
[BUG]: cuda::std::extents::static_extent truncates cuda::std::dynamic_extent when index_type is unsigned int
Dec 21, 2023
Is this a duplicate?
Type of Bug
Compile-time Error
Component
libcu++
Describe the bug
It seems that when index_type in cuda::std::extents is unsigned int then dynamic extents are truncated to a smaller type. It works correctly if index_type is int, not sure about other types.
How to Reproduce
Expected behavior
cuda::std::extents::static_extent should return cuda::std::dynamic_extent for dynamic extents regardless of what index_type is
Reproduction link
https://godbolt.org/#z:OYLghAFBqd5QCxAYwPYBMCmBRdBLAF1QCcAaPECAMzwBtMA7AQwFtMQByARg9KtQYEAysib0QXACx8BBAKoBnTAAUAHpwAMvAFYTStJg1DIAruiakl9ZATwDKjdAGFUtEywYgATKUcAZPAZMADl3ACNMYglpAAdUBUI7Bhc3D29SOITbAQCg0JYIqKlLTGtshiECJmICFPdPLhKypMrqglyQ8Mi9BSqaurTG3raO/MKJAEpLVBNiZHYOAFIvAGZA5DcsAGpFladTcwB6XvRDggBPGMwAfQJiJkIFXexFjQBBZbWGDbNMHb2DkxjgRTix0AoYoZnq8Pu9AgQtiwHgwIBMYYsAOwAIRhWzxW0BIBAJyJmFUBEYBCeexMDASwCC6C28NIBLMTCJJJA6HOzBYeGQ1zJFMEzy2N1p9MZEC4aJWWJ273xbPMnJBpPJlOpThZKo5xPV3N5rAFQs1opW2HF1ylmHQMrlCvRSvxw1sgqYCiUNQghIN6CJeAUNtYNwAbrsnFgNhcrhAJXS8Ay7QA6N2m4WUiAaCZTLbR2ixzDxm1Jxlpqrus0igjZ3PPR2412V02e721hO29AVphVzOCOv/AAiuyH1q7Pb75trOcbLrx6Y9XsiHeukrLqcX1azOeHo71aoDRr5Genc7eyq3bZXJYnW/7M4me5WY79XJ5J8FD/P6IxQ44Uy0JwACsvCeBwWikKgnBOHIQ4Xk4yw4l4CoKDMcx/J8PCkAQmgAVMADWIDAVwKaSFwACcKxcNRwErBoAAcGIUcBwH6JwkhgXhUGcLwCggBoOF4VMcCwEgaAsDEdCROQlASVJ9BRAwYbIMgXCrCYjQ0IWkT8RAYTcWEgTVOcnDYUZzDEOcADyYTaJgNhmbwElsII1kMLQpkQbwWBhCYwBOGItD8dwPmYEiRjiN5pD4MQDm2GGmAhZBZIOSYFLcfCpTcbQeBhPcVkuFg3F3HgLBOVMVAGMACgAGp4JgADu1lXOB2H8IIIhiOwxQdfIShqNxuiNAYRgoOy%2Bh5fxkBTKgMTlCFvCoIlxDEHgWDTaiTTxUkDgMM4rj1Ho/iBJ0BTdI0mSJAIAwNBk8TXQwoxdEU202C0fS1IdgxveUrQ1M952vcM/TfXdIPtKdYwXVMaGzPMkzsRwoGkOBkHQRwWzBLVThOFs6kpisKZcFsEC4IQJA7Kssq8Lh3m5qQRHAcTXgMQxFFcBiwEURRDEAGzMWxQEcJxqPcRjfECUJ9OkKJiAgDMBAxOlsm%2BqgknScQwShpw2BDgA4qTZJXGtrlVLQWxxVVO0CBMvB2hTa0BlpshdeIvWyIoKjqNFw2kI19wxBVSMo2jS2cNZ6XKwiqBUFjON4wTRMkxALga4pVPUXb0taAzRFeBRKYMSsGIYnzHO8wxBesULHFcdFEuWFLdO57LMDy1gYYCpgqvyZr2tsJw2O4/jXiE8TYVdwjHD2/gRBO3ofVuz10h9V7g2%2Bz0pQ2548b7bdx37YD4yXQ95QH6fWRJMfF2/R9bQX3fAj/ZDeQvT0n2PxDN9FFMdyYJgdaAlAIgXrujTgQ5MBTz%2BPVJqkR44jyTsTUm5N56Z0aFsNOCl4FYWzi3fCjMJBEz5lIDQXhgJswYhoFiGINArCRqLMOPEZ5N0EvghmwsvBgPDiw9hUwVoJHsJIIAA%3D%3D
Operating System
No response
nvidia-smi output
No response
NVCC version
No response
The text was updated successfully, but these errors were encountered: