cling/test/CodeUnloading/CircularReferences.C

//------------------------------------------------------------------------------
// CLING - the C++ LLVM-based InterpreterG :)
//
// This file is dual-licensed: you can choose to license it under the University
// of Illinois Open Source License or the GNU Lesser General Public License. See
// LICENSE.TXT for details.
//------------------------------------------------------------------------------

// RUN: cat %s | %cling 2>&1 | FileCheck %s

.storeState "preUnload"
.rawInput 1
int g(); int f(int i) { if (i != 1) return g(); return 0; } int g() { return f(1); } int x = f(0);
.rawInput 0
.undo
.compareState "preUnload"
//CHECK-NOT: Differences
float f = 1.1
//CHECK: (float) 1.1
int g = 42
//CHECK: (int) 42
.q
Refer to license in test and demo files. 2014-01-07 14:57:02 +04:00			`//------------------------------------------------------------------------------`
			`// CLING - the C++ LLVM-based InterpreterG :)`
			`//`
			`// This file is dual-licensed: you can choose to license it under the University`
			`// of Illinois Open Source License or the GNU Lesser General Public License. See`
			`// LICENSE.TXT for details.`
			`//------------------------------------------------------------------------------`

Enhance the support for removing global values from the module with JIT lock. When the machine code was generated the JIT retains a lock to the global values so they don't go out of sync. In the cases of circular references like: int g(); int f() {g();} int g() {f();} we cannot count on the removal order to get rid of the uses. We need to use the replaceAllUsesWith. This is however tricky because the JIT already generated the code for f and g and it doesn't make sense to replace anything with anything else. Thus in order to support that we need to hack one of the JIT callbacks which prevents the replace of values of already emitted code. 2013-10-29 06:00:27 +04:00			`// RUN: cat %s \| %cling 2>&1 \| FileCheck %s`

			`.storeState "preUnload"`
			`.rawInput 1`
			`int g(); int f(int i) { if (i != 1) return g(); return 0; } int g() { return f(1); } int x = f(0);`
			`.rawInput 0`
Replace .U with .undo 2014-03-31 12:44:19 +04:00			`.undo`
Enhance the support for removing global values from the module with JIT lock. When the machine code was generated the JIT retains a lock to the global values so they don't go out of sync. In the cases of circular references like: int g(); int f() {g();} int g() {f();} we cannot count on the removal order to get rid of the uses. We need to use the replaceAllUsesWith. This is however tricky because the JIT already generated the code for f and g and it doesn't make sense to replace anything with anything else. Thus in order to support that we need to hack one of the JIT callbacks which prevents the replace of values of already emitted code. 2013-10-29 06:00:27 +04:00			`.compareState "preUnload"`
			`//CHECK-NOT: Differences`
			`float f = 1.1`
			`//CHECK: (float) 1.1`
			`int g = 42`
			`//CHECK: (int) 42`
			`.q`