Mercurial > hg > truffle

comparison test/compiler/regalloc/C1ObjectSpillInLogicOp.java @ 13044:a905d33ce13a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
8027751: C1 crashes in Weblogic with G1 enabled Summary: Keep T_OBJECT operands in registers for logical operations on x64 Reviewed-by: kvn, roland
author iveresov
date Tue, 05 Nov 2013 00:59:30 -0800
parents
children ad45ebfba060
comparison
equal deleted inserted replaced
13042:208ebea980f8 13044:a905d33ce13a
1 /*
2 * Copyright (c) 2013, Oracle and/or its affiliates. All rights reserved.
3 * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
4 *
5 * This code is free software; you can redistribute it and/or modify it
6 * under the terms of the GNU General Public License version 2 only, as
7 * published by the Free Software Foundation.
8 *
9 * This code is distributed in the hope that it will be useful, but WITHOUT
10 * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
11 * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
12 * version 2 for more details (a copy is included in the LICENSE file that
13 * accompanied this code).
14 *
15 * You should have received a copy of the GNU General Public License version
16 * 2 along with this work; if not, write to the Free Software Foundation,
17 * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
18 *
19 * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
20 * or visit www.oracle.com if you need additional information or have any
21 * questions.
22 */
23
24 /*
25 * @test
26 * @bug 8027751
27 * @summary C1 crashes generating G1 post-barrier in Unsafe.getAndSetObject() intrinsic because of the new value spill
28 * @run main/othervm -XX:+UseG1GC C1ObjectSpillInLogicOp
29 *
30 * G1 barriers use logical operators (xor) on T_OBJECT mixed with T_LONG or T_INT.
31 * The current implementation of logical operations on x86 in C1 doesn't allow for long operands to be on stack.
32 * There is a special code in the register allocator that forces long arguments in registers on x86. However T_OBJECT
33 * can be spilled just fine, and in that case the xor emission will fail.
34 */
35
36 import java.util.concurrent.atomic.*;
37 class C1ObjectSpillInLogicOp {
38 static public void main(String[] args) {
39 AtomicReferenceArray<Integer> x = new AtomicReferenceArray(128);
40 Integer y = new Integer(0);
41 for (int i = 0; i < 50000; i++) {
42 x.getAndSet(i % x.length(), y);
43 }
44 }
45 }