Delete RuntimeTest freeMemory test

Test was flaky due to bad assumptions, Runtime.freeMemory is already
tested by test_memory, test_gc.

Bug: 17448025

(cherry picked from commit e2233ca92da0339686da18db4a1e27b9a4c76b91)

Change-Id: I88d09ee5cd1c4e34c97814afd2cbadc870222738
Libcore: Change miranda modifier flag

Flag was changed in ART. Move accordingly.

Bug: 16161620

(cherry picked from commit 93b153dea95bfa5068d2146228d62c3e4e905da2)

Change-Id: I2f591d53b7d1559171e70aaaf22225d94b4882f5
Removing some compiler-warning suppressions from EnumMap

The original motivation was to fix a report that
line 162 does not compile with newer compilers:
https://code.google.com/p/android/issues/detail?id=73244

There are a lot of compiler warning suppressions which made
the problem less obvious than it should have been.
The fact it compiled before was possibly a compiler bug.
This change removes a lot of the suppression, and where it
cannot be removed it narrows the scope to just local-variable
declarations. One method-level suppression remains.

This commit also adds a bug fix for situations where the raw
type is being used and an EnumMap is being created from an
existing Map. Previously a NullPointerException would have been
thrown if the first key found was not actually an enum, now a
ClassCastException will be thrown.

Some additional comments have been added and some loops made
into foreach.

Bug: https://code.google.com/p/android/issues/detail?id=73244
Change-Id: I7f23744dc55237a94e5906e77720a9595caa64e8
Fix ZoneInfo.useDaylightTime()

Currently implemented is "are there any offset transitions
in the future?".
This is wrong: Transitions may occur in the future because
of DST, but can also occur for other reasons (e.g. if the
raw offset for a zone changes).

We should be implementing: Is the currently active transition,
or any transition in the future, one that has
isDst == true.

This was causing a test failure in
libcore.java.util.TimeZoneTest#testDisplayNames
for Asia/Novokuznetsk and Europe/Simferopol for
tzdata2014g. This is because they have a transition entry
for October 26, 2014 (i.e. in the future).

For each, the existance of the transition entry is not
due to an offset change at all:
For Asia/Novokuznetsk it is because the abbreviation
for the zone changes on that date (information we don't
curently use).
For Europe/Simferopol it is because the offset from
UTC changes on that date (but there is no actual DST
transtion).

Bug: 17377276

(cherry-picked from commit d42af6ed0fec3cfca52912b0d8b3b459e72be4b4)

Change-Id: I148503280b8dee653bac32eec3aa58d232102628
Merge "Libcore: Change miranda modifier flag"
Merge "Delete RuntimeTest freeMemory test"
Merge "Fix ZoneInfo.useDaylightTime()"
Merge "Removing some compiler-warning suppressions from EnumMap"