NNAPI VTS: use max time point instead of uint64_t max
Bug: 149441015 Test: mma Test: VtsHalNeuralnetworksV1_3TargetTest Change-Id: Ic74f83242cbe04a4cec47adbfc51002fdf8bb47d
This commit is contained in:
parent
9f1197d48b
commit
79d6bb1ad2
1 changed files with 4 additions and 2 deletions
|
@ -67,8 +67,10 @@ static OptionalTimePoint makeOptionalTimePoint(DeadlineBoundType deadlineBoundTy
|
|||
deadline.nanosecondsSinceEpoch(nanosecondsSinceEpoch);
|
||||
} break;
|
||||
case DeadlineBoundType::UNLIMITED: {
|
||||
uint64_t unlimited = std::numeric_limits<uint64_t>::max();
|
||||
deadline.nanosecondsSinceEpoch(unlimited);
|
||||
const auto maxTime = std::chrono::time_point<std::chrono::steady_clock,
|
||||
std::chrono::nanoseconds>::max();
|
||||
const uint64_t nanosecondsSinceEpoch = maxTime.time_since_epoch().count();
|
||||
deadline.nanosecondsSinceEpoch(nanosecondsSinceEpoch);
|
||||
} break;
|
||||
}
|
||||
return deadline;
|
||||
|
|
Loading…
Reference in a new issue