[BUG] seq_v unusued, but set causing complaints in upstream PyTorch compilation

[Skylion007]

Describe the bug
A clear and concise description of what the bug is.
build trace:
https://hud.pytorch.org/pr/pytorch/pytorch/131493#32406967080

Steps/Code to reproduce bug
Follow this guide http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports to craft a minimal bug report. This helps us reproduce the issue you're having and resolve the issue more quickly.

• try to compile @eqy's PR here [CUDA][CUTLASS][submodule] Fixes for CUTLASS upgrade pytorch/pytorch#131493 . Compilation throws errors due to unused variables. [maybe_unused] or removing them could be used to fix them.

Expected behavior
A clear and concise description of what you expected to happen.

CUTLASS does not cause errors in downstream projects due to unused variables.

Environment details (please complete the following information):

• Environment location: [Bare-metal, Docker, Cloud(specify cloud provider)]

Additional context
Add any other context about the problem here.

[Skylion007]

This seems like a straightforward fix @eqy . Just add '[maybe_unused]` annotations to this lambda (for both order and seq_v) would likely fix it?

cutlass/include/cute/stride.hpp

Line 456 in b0e09d7

return seq_v;

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.