Currently our java/util/zip/InflaterInputStream differs from Classpath's. Putting ours into Classpath causes regressions there. Putting Classpath's into libgcj causes regressions in libgcj. Probably one or both Inflater implementations is incorrect in some way.
Note that we need more mauve tests in this area before fixing the problem. The current tests don't catch the bug(s).
This is no longer a problem. I think the PR 27271 fix cleaned up the lingering problem. (It is hard to be sure since this report is so vague...)
I don't think this is fixed yet. It seems libgcj and classpath still have different nflaterInputStream implementations. See also the following thread were they were supposed to be merged, but a regression was found and the merge was reverted: http://developer.classpath.org/pipermail/classpath-patches/2006-March/000940.html
All the problems were ironed out and now this is fixed. As of 4.2 we only differ in Deflater and Inflater, which is tolerable.