Package-private access checking in GCJ 3.3

[Tom Tromey]

>>>>> "Ranjit" == Ranjit Mathew <rmathew@hotmail.com> writes:

Ranjit> In any case, as Tom predicted, this kludge still exposes
Ranjit> a number of illegal accesses to package-private members 
Ranjit> in libgcj.

How very bogus of us.

Let's definitely fix these.  However, one issue to look at is whether
exposing these fields and methods will cause us security problems in
the future.  If so, we may need to take some other action, for
instance moving classes into a different package, or moving accesses
into native code.

Tom