Skip to content

Fix a compiler warning#555

Merged
magnatelee merged 1 commit intonv-legate:branch-22.10from
magnatelee:fix-compile-warning
Aug 24, 2022
Merged

Fix a compiler warning#555
magnatelee merged 1 commit intonv-legate:branch-22.10from
magnatelee:fix-compile-warning

Conversation

@magnatelee
Copy link
Contributor

Some compiler doesn't like a single if-else statement in a value-returning function that has a return statement in both branches.

@magnatelee magnatelee requested a review from manopapad August 23, 2022 06:27
@magnatelee
Copy link
Contributor Author

@manopapad please confirm that this PR fixes the warning you're seeing

Copy link
Contributor

@manopapad manopapad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this fixes the warning. The actual code works with and w/o this fix, so the emitted code doesn't change, it's probably just a false positive coming from nvcc.

@magnatelee magnatelee merged commit 1290fe0 into nv-legate:branch-22.10 Aug 24, 2022
@magnatelee magnatelee deleted the fix-compile-warning branch August 24, 2022 04:47
jjwilke pushed a commit to jjwilke/cunumeric that referenced this pull request Sep 2, 2022
manopapad pushed a commit that referenced this pull request Feb 18, 2025
This pulls some CMake code from #528 to improve the logic around initializing the `CMAKE_CUDA_ARCHITECTURES` variable in the project. It fixes builds using CMake directly and offers more robust logic in light of `rapids-cmake` deprecating and removing the use of empty string there.

This fixes issue #554.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants