From 34e069606d6f1698cd3c33b39e72b79ae27e1c7b Mon Sep 17 00:00:00 2001 From: Elliott Hughes Date: Mon, 9 Apr 2012 13:55:55 -0700 Subject: Remove the useless "suspend count already zero" message for new threads. We can actually detect the expected case of this warning ourselves, and not emit it. Then we can upgrade the WARNING to a FATAL. I also tripped over the fact that the operator<< for Thread::State was out of date, so I've moved the Thread enums up to namespace scope so the script can automatically generate correct operator<< implementations for us. (All the high-numbered thread states have been off by one for a couple of weeks.) Change-Id: I5de573d33d641e5a3cba87b370e9620c8c66e633 --- src/java_lang_Object.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/java_lang_Object.cc') diff --git a/src/java_lang_Object.cc b/src/java_lang_Object.cc index f95d1a1518..7c79fc1aed 100644 --- a/src/java_lang_Object.cc +++ b/src/java_lang_Object.cc @@ -22,7 +22,7 @@ namespace art { static jobject Object_internalClone(JNIEnv* env, jobject javaThis) { - ScopedThreadStateChange tsc(Thread::Current(), Thread::kRunnable); + ScopedThreadStateChange tsc(Thread::Current(), kRunnable); Object* o = Decode(env, javaThis); return AddLocalReference(env, o->Clone()); } -- cgit v1.2.3-59-g8ed1b