|
|
Bugzilla Link |
447 |
Created on |
Jul 11, 2008 12:28 |
Resolution |
FIXED |
Resolved on |
Jul 12, 2008 20:09 |
Version |
1.00beta |
OS |
Linux |
Architecture |
PC |
Attachments |
error.sac |
Extended Description
Created an attachment (id=489)
source code
as of rev15771:
run sac2c error.sac -v4 -b11:cyc:cse:2 -noprelude and you obtain:
a = [ 1, 2, 3, 4 ];
b = [ [ 1, 2, 3, 4 ], [ 1, 2, 3, 4 ] ];
b__SSA0_1 = b;
iv = [ 1 ];
b__SSA0_1__SSA2_1 = _modarray_AxVxA_( b__SSA0_1, iv, a);
iv__SSA2_1 = [ 0 ];
_wldp_54 = sacprelude::sel( iv__SSA2_1, b);
b__SSA0_1__SSA2_2 = _modarray_AxVxA_( b__SSA0_1__SSA2_1, iv__SSA2_1, _wldp_54);
Now running cf ( sac2c error.sac -v4 -b11:cyc:cf:2 -noprelude) we get:
a = [ 1, 2, 3, 4 ];
b = [ [ 1, 2, 3, 4 ], [ 1, 2, 3, 4 ] ];
b__SSA0_1 = b;
iv = [ 1 ];
b__SSA0_1__SSA2_1 = [ [ 1, 2, 3, 4 ], [ 1, 2, 3, 4 ] ];
iv__SSA2_1 = [ 0 ];
_wldp_54 = sacprelude::sel( iv__SSA2_1, b);
b__SSA0_1__SSA2_2 = [ [ _wldp_54, 2, 3, 4 ], [ 1, 2, 3, 4 ] ];
^^^^^^^^^
OUCH!!!
which subsequently (correctly) leads to array-element incompatability errors
(see masterruns E-04.sac etcetcetc)