test/compiler/arraycopy/TestArrayCopyOverflowArguments.java

@@ -26,14 +26,17 @@
  * @summary Test that overflowed integers passed to arraycopy don't do any harm. This might
  *          be the case on platforms where C-code expects that ints passed to a call
  *          are properly sign extended to 64 bit (e.g., PPC64, s390x). This can fail
  *          if slow_arraycopy_C() is commpiled by the C compiler without any imlicit
  *          casts (as spill stores to the stack that are done with 4-byte instruction).
- * @run main/othervm -XX:-BackgroundCompilation -XX:-UseOnStackReplacement TestArrayCopyOverflowArguments
  *
+ * @run main/othervm -XX:-BackgroundCompilation -XX:-UseOnStackReplacement
+ *                   compiler.arraycopy.TestArrayCopyOverflowArguments
  */
 
+package compiler.arraycopy;
+
 public class TestArrayCopyOverflowArguments {
 
     // Without volatile the overflowing computation was moved up and then
     // spilled to the stack. The 32-bit spill store caused proper rounding.
     static volatile int mod = Integer.MAX_VALUE;