…nit.c Change-Id: I5549031ae6d6414797a22421e6bf62d1be08ac9a
x86 doesn't (yet) support pre-linking and we need to disable it until it does. Change-Id: Icfba41c364ed934632386e2fa7f50844dabd126e Signed-off-by: Bruce Beare <email@example.com>
Merge commit '9a2b2f7678128a5385c83ea393d73cf3cdfcbe46' into froyo-plus-aosp * commit '9a2b2f7678128a5385c83ea393d73cf3cdfcbe46': Don't build dx if it's an app-only build.
This patch adds a native implementation for availableProcessors(), replacing the hardcoded "always return 1" implementation. It uses sysconf(_SC_NPROCESSORS_ONLN) to get the number of online processors. Signed-off-by: Christian Bejram <firstname.lastname@example.org>
…taticTest#test_returnChar. CALLABI.S was not returning unsigned shorts correctly. Change-Id: Ia6b443d41a96b0f65739c0b16a0ddb39f7eb33fa
Introduced originally in bionic by https://review.source.android.com/#change,14740 Change-Id: I624dba3847975b5cb3c0543a5fb6d6f6986e11b5 Signed-off-by: André Goddard Rosa <email@example.com>
Use of the LDRD instruction form LDRD Rt, Rt2, [Rn, Rm] has restrictions on the register combinations - specifically if Rt or Rt2 is equal to Rn or Rm the behaviour is defined as 'UNPREDICTABLE'. Change-Id: I19834783865e07897cc7012367e698447f023ce6
Merge commit '962f896e1eeb159a6a2ac7a560708939cbb15575' into froyo-plus-aosp * commit '962f896e1eeb159a6a2ac7a560708939cbb15575': Add /proc/pid/task/tid/schedstat info to thread stack dumps
This lets us see whether a usually-blocked thread is actually making progress in between stack snapshots. Change-Id: If191627e4572457579d5f330d31bde86b8ce4ec5
…evelopers Merge commit '2b469f82df14749c67da43f073fd7a9b6b1ccd74' into froyo-plus-aosp * commit '2b469f82df14749c67da43f073fd7a9b6b1ccd74': Jit: Fix for 2717275 First JIT bug reported by external developers
The JIT was incorrectly keeping a short value in a floating point register rather than copying it to a core register before storing. There was an assert to catch this case, but asserts don't fire in production builds. The fix is safe and simple - just exclude this case from the "optimization". Change-Id: I38f1865da11ef3f78213f84967d4737e066b9c68
Due to compatability issues with some sites, disable this SSL extension which wasn't present in Eclair. See also: b/2682876 Some ssl sites cause "A secure connection could not be established" error Change-Id: Ib42fb249eb0f8d645ae3f983c77cb278ca54f946
Merge commit 'f3377c64212d5ebda0799d42659bde3e8f488b29' into froyo-plus-aosp * commit 'f3377c64212d5ebda0799d42659bde3e8f488b29': Remove test runner tool vogar from Froyo.
This tool has been open sourced independently and it will be quite awkward for external contributors who attempt to use or contribute to this dead copy. This code is test only and not used by the production runtime. http://code.google.com/p/vogar/ Change-Id: Ib53bdfdb600330e1a2f200b5747305fc527a78a6
…dump a stacktrace Gutted OpenSSLSocketImpl finalizer. The comment from the code (excepted below) explains in detail the trouble of having the finalizer do anything more than touch its the instances own state due to unpredictable order of finalization and the future possability of parallel finalization. /* * Just worry about our own state. Notably we do not try and * close anything. The SocketImpl, either our own * PlainSocketImpl, or the Socket we are wrapping, will do * that. This might mean we do not properly SSL_shutdown, but * if you want to do that, properly close the socket yourself. * * The reason why we don't try to SSL_shutdown is that there * can be a race between finalizers where the PlainSocketImpl * finalizer runs first and closes the socket. However, in the * meanwhile, the underlying file descriptor could be reused * for another purpose. If we call SSL_shutdown after that, the * underlying socket BIOs still have the older file descriptor * and will write the close notify to some unsuspecting * reader. */ Tested extensively in mainline with existing tests.xnet.AllTests as well as new javax.net.ssl tests. Sanity tested in froyo with tests.xnet.AllTests and browser testing. Change-Id: I85e0e086b43b2ad79304f2cf42721d09cc41a5f4
Merge commit '818164b87a9c08a938c371d8b47987a3af06d6f6' into froyo-plus-aosp * commit '818164b87a9c08a938c371d8b47987a3af06d6f6': Revert "Plug leak in class initialization."
This reverts commit d07cf9d. Bug: 2664424 Change-Id: I1a36469757f2f20fb29b3bcf04e2a23aa7b72dca
Don't add static fields and methods to the resolved-items table if the defining class is still being initialized. If we do, other threads can then access those fields and methods without first performing an "is the class initialized" test. We will end up performing static field and method resolution more often now than before. On a Nexus One, zygote class preload time went from 2227ms to 2239ms (i.e. the performance difference is in the noise). Bug 2655384. Change-Id: Ib0c285ef23d58ae709be65f09efb68e73f982084
…ion. This started off as incremental changes, but it ended up going far enough that it earned the "rewrite" badge. System.getProperty() is not called for every HTTP connection. This is slightly controversial, but the old code had to bend over backwards to support dynamic pool changes, and it didn't even support the case when the pool shrank but not to 0. The new code doesn't do I/O within static synchronized blocks. This should reduce contention described here: http://b/issue?id=2606547 Also: simpify implementation, prettier names, more focused doc. Originally submitted to dalvik-dev. https://android-git.corp.google.com/g/49309 Change-Id: I815c3123838b29cd2d9b39346e5c2486e1f5a2d2
Merge commit '4751c150542ec282f6c6d58984974edec6c0a045' into froyo-plus-aosp * commit '4751c150542ec282f6c6d58984974edec6c0a045': Fixing bulk reads in ByteArray.MyInputStream
This has never worked properly, but it didn't matter until recently because neither the JDK's nor early Dalvik's DataInputStream was exercising it. But in 2.0, Dalvik's DataInputStream prefers bulk reads, which exercises this code when run on-device. http://code.google.com/p/android/issues/detail?id=8115 The problem was that System.arraycopy call didn't include the start offset in the call.