When the sign of either of the operands is known, it is possible to
determine what the saturating value will be without having to compute it
using the sign bits.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Looks reasonable to me.
llvm/test/CodeGen/AArch64/aarch64-saturating-arithmetic.ll | ||
---|---|---|
2 | You can drop -verify-machineinstrs, -O3 and --check-prefixes=CHECK here. -verify-machineinstrs is enabled under EXPENSIVE_CHECKS, and doesn't need to be added to most tests. -O3 rarely differs from the default of -O2 for llc. --check-prefixes=CHECK is already the default. | |
209 | Can you please commit the tests with baseline checks and then rebase the patch over that? See https://llvm.org/docs/TestingGuide.html#precommit-workflow-for-tests. |
You can drop -verify-machineinstrs, -O3 and --check-prefixes=CHECK here. -verify-machineinstrs is enabled under EXPENSIVE_CHECKS, and doesn't need to be added to most tests. -O3 rarely differs from the default of -O2 for llc. --check-prefixes=CHECK is already the default.