tag 6bed9c4a2a0a5ab0930f9f69f6e34fee6088f97b
tagger The Android Open Source Project <initial-contribution@android.com> Mon Dec 11 10:14:05 2017 -0800
object 276a33a1b55896587d24a8a0032a853b82a96dec

Android O IOT Preview 6 (4475743)

commit 276a33a1b55896587d24a8a0032a853b82a96dec
author Hans Boehm <hboehm@google.com> Tue Oct 31 14:23:37 2017 -0700
committer Hans Boehm <hboehm@google.com> Tue Oct 31 14:36:59 2017 -0700
tree 72e87abb578c52a73fb90e5078022843321d9899
parent dfed3c6d374ce288e7ba5bf987ccaed3ba14eea6

Make signum and compareTo check for interrupts

Bug: 68670525

Unless we check for interrupts some comparisons will run forever
uninterruptibly.

If the client, for example, compares sqrt(11) - sqrt(11) to zero,
and then interrupts, it may still take quite a while for the interrupt
to be recognized, since each iteration of the compare loop can take
seconds. For the Android Calculator, this is usually not directly
visible, except that the compute thread will continue to use cpu
for several seconds.

Test: Ran Android calculator tests, manually exercised this case.
Change-Id: I0fe0922a8ee68bf0e08ce59c0d8c372ad10ef419