From 82bcbebce43f0227f506d75a5b764b6847041bae Mon Sep 17 00:00:00 2001 From: Ben Cheng Date: Mon, 1 Oct 2012 10:30:31 -0700 Subject: Initial check-in of gcc 4.7.2. Change-Id: I4a2f5a921c21741a0e18bda986d77e5f1bef0365 --- gcc-4.7/libjava/mauve-libgcj | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 gcc-4.7/libjava/mauve-libgcj (limited to 'gcc-4.7/libjava/mauve-libgcj') diff --git a/gcc-4.7/libjava/mauve-libgcj b/gcc-4.7/libjava/mauve-libgcj new file mode 100644 index 000000000..4d4cf5bc1 --- /dev/null +++ b/gcc-4.7/libjava/mauve-libgcj @@ -0,0 +1,25 @@ +# Config file that tells mauve about the `libgcj' tag. +JDK1.0 +JDK1.1 +JDK1.2 +JDK1.3 +JDK1.4 +JLS1.0 +JLS1.1 +JLS1.2 +JDBC1.0 +JDBC2.0 + +# The following tests seem to hang or crash the testsuite. +# This a problem when running Mauve "standalone". +!java.lang.reflect.Array.newInstance + +# These are almost certainly buggy test cases. +# The behaviour of the garbarge collector cannot be predicted. +# Note the . at the end so we do test java.lang.reflect +!java.lang.ref. + +# Tests for not yet implemented classes and/or methods. +!java.awt.event.MouseEvent.modifiersEx +!org.omg. +!javax.rmi -- cgit v1.2.3