fb0ec0e650bf8be35acb0d47da0311a7c446aa33 |
|
14-Jan-2011 |
Elliott Hughes <enh@google.com> |
Remove useless android-changed comments. I've changed useful ones to regular comments or TODOs, as appropriate. I've left ones in code like java.util.concurrent where we really are tracking an upstream source, making the change markers useful. I've left a handful of others where I intend to actually investigate the implied TODOs before deciding how to resolve them. Change-Id: Iaf71059b818596351cf8ee5a3cf3c85586051fa6
|
171dc20afe5071d5cbfad7103903bfa2c1f8d00f |
|
02-Sep-2010 |
Elliott Hughes <enh@google.com> |
Use idiomatic Java "type[] id" syntax instead of "type id[]". I've left xalan and the other xml filth alone, as usual. Change-Id: I6be274501fff73e67ca6b3c872704988e0e30486
|
fd3f1748b8627e8b6ee907bdaad4cbf2abd7403b |
|
24-Aug-2010 |
Jesse Wilson <jessewilson@google.com> |
Fix concurrency issues in BigInteger. Also go over the class documentation and formatting and give it some long overdue attention. The docs are still far from perfect! But this should get rid of the most obvious problems. See http://b/issue?id=2785595 Change-Id: Iea40975b95a850702a4cdc693f65e4eaff0dd8b0
|
63710430c17f7c0a1e74b926cd21248fde8e9589 |
|
11-Jun-2010 |
Elliott Hughes <enh@google.com> |
Make BigInteger thread-safe. We were sharing an openssl BN_CTX between threads, which is unsafe. Stop doing that, creating BN_CTXes on demand (which seems to be what openssl does internally). For 1024-bit integers, this makes division faster, multiplication slower, and makes no convincing difference to gcd. I instrumented a build to report any time one of the methods that needs a BN_CTX gets called, and couldn't find anywhere they're used during boot or https browser usage. (These things do use BigInteger; they just don't use the methods this change affects.) Bug: 2652542 Change-Id: I98c94b41df95566cb4c8598f299911e641f72f63
|
cec4dd4b1d33f78997603d0f89c0d0e56e64dbcd |
|
26-Apr-2010 |
Peter Hallam <peterhal@google.com> |
merge more modules into luni
|