Repository navigation
Workaround for __builtin_fmaxf/fminf in clang+Arm64 (nightly build failure) - #11496
Conversation
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: NVIDIA/cccl/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe change adds host ARM64 Clang-specific NaN checks to ChangesARM64 NaN handling
Priority: ⬇️ Low Change: Bug fix Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 83d91acc-d041-483c-9ba8-a635fc1f7984
📒 Files selected for processing (1)
libcudacxx/include/cuda/std/__cmath/min_max.h
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.
This comment has been minimized.
This comment has been minimized.
miscco
left a comment
There was a problem hiding this comment.
Question: Why is this not changing fmin when that is also affected?
the last commit was not pushed. Thanks for reminding me! |
This comment has been minimized.
This comment has been minimized.
🥳 CI Workflow Results🟩 Finished in 3h 08m: Pass: 100%/221 | Total: 3d 02h | Max: 1h 57m | Hits: 99%/607373See results here. |
Description
Clang lowers fmax/fmin to AArch64 HW instructions, which returns quite NaN instead of signaling NaNs. Releted LLVM issue llvm/llvm-project#176624