cling

gamzinav/cling

Fork 0

Commit Graph

Author	SHA1	Message	Date
Vassil Vassilev	666437108e	Replace .U with .undo	2014-03-31 14:03:09 +02:00
Axel Naumann	d240bd5de8	Refer to license in test and demo files.	2014-01-07 12:02:58 +01:00
Vassil Vassilev	a08152d576	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 20:19:24 +01:00

Author

SHA1

Message

Date

Vassil Vassilev

666437108e

Replace .U with .undo

2014-03-31 14:03:09 +02:00

Axel Naumann

d240bd5de8

Refer to license in test and demo files.

2014-01-07 12:02:58 +01:00

Vassil Vassilev

a08152d576

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 20:19:24 +01:00

3 Commits