Displaying 3 results from an estimated 3 matches for "i_x".
Did you mean:
_x
2013 Jan 01
0
[LLVMdev] [DragonEgg] [Polly] Should we expect DragonEgg to produce identical LLVM IR for identical GIMPLE?
...get in the way of the diffing.
<bb X>:
# k_X = PHI <k_X(X), k_X(X)>
- D.X_X = ny;
+ D.X_X = *ny_X(D);
j_X = X;
if (j_X <= D.X_X)
goto <bb X>;
@@ -16,7 +74,7 @@
<bb X>:
# j_X = PHI <j_X(X), j_X(X)>
- D.X_X = nx;
+ D.X_X = *nx_X(D);
i_X = X;
if (i_X <= D.X_X)
goto <bb X>;
@@ -25,48 +83,36 @@
<bb X>:
# i_X = PHI <i_X(X), i_X(X)>
- D.X_X = xy.data;
D.X_X = (integer(kind=X)) i_X;
D.X_X = (integer(kind=X)) k_X;
- D.X_X = xy.dim[X].stride;
- D.X_X = D.X_X * D.X_X;
+ D.X_X = D.X_X * stri...
2012 Dec 31
3
[LLVMdev] [DragonEgg] [Polly] Should we expect DragonEgg to produce identical LLVM IR for identical GIMPLE?
Dear all,
In our compiler we use a modified version LLVM Polly, which is very
sensitive to proper code generation. Among the number of limitations, the
loop region (enclosed by phi node on induction variable and branch) is
required to be free of additional memory-dependent branches. In other
words, there must be no conditional "br" instructions below phi nodes. The
problem we are facing
2004 Jan 27
11
test
The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.