aboutsummaryrefslogtreecommitdiff
path: root/vm/compiler/codegen/arm/CodegenDriver.c
diff options
context:
space:
mode:
authorCarl Shapiro <cshapiro@google.com>2010-12-22 12:21:01 -0800
committerCarl Shapiro <cshapiro@google.com>2010-12-22 12:28:44 -0800
commitdafced82f3cd926daecd14fb99cf4a7bbc11994f (patch)
tree003d222cc0dbdb79251cfabe41835d96f0ff236b /vm/compiler/codegen/arm/CodegenDriver.c
parenta7a2d108b10803e2b96a56ffb3957561f5534e79 (diff)
Restore a few external allocation constants for compatibility.
Aspects of the external allocation facility were exposed through the VMDebug getAllocCount method. In a previous change I removed all of the references to external allocation from getAllocCount. This had the unfortunate side effect of breaking some CTS tests and causing the VM to abort if the old constants were provided to getAllocCount on an asserts enabled dalvik build. The straight forward workaround seems to be to restore the special treatment of these values in getAllocCount for as long as we support the public interfaces of the external allocation facility. An easier way out may have been to make the failure case of getAllocCount return 0 instead of -1 and aborting on an asserts build. Without some analysis of API usage in market I would prefer to not change the -1 return value to 0 as it seems the thread counts currently return -1. This change also eliminates the conditional export of the enum values related to external allocation. Those values are published API so it makes no sense to maintain a way to guard their inclusion. Change-Id: I49c173e0ec305536760c7aec15eebdc29213fc56
Diffstat (limited to 'vm/compiler/codegen/arm/CodegenDriver.c')
0 files changed, 0 insertions, 0 deletions