Displaying 1 result from an estimated 1 matches for "__go_new_nopointers".
2011 Sep 13
1
[LLVMdev] Weird GIMPLE by gccgo
...m currently facing is that when
compiling Go, GCC tends to generate GIMPLE calls that don't have the
correct type (or so it seems to me :) ). For instance, when compiling
ddd.go from the Go testsuite, I get this:
i.91 = i;
D.785 = i.91.__methods;
D.786 = D.785->Sum;
D.787 = __go_new_nopointers (16);
MEM[(int[4] *)D.787][0] = 2;
MEM[(int[4] *)D.787][1] = 3;
MEM[(int[4] *)D.787][2] = 5;
MEM[(int[4] *)D.787][3] = 7;
D.788.__values = D.787;
D.788.__count = 4;
D.788.__capacity = 4;
D.789 = i.91.__object;
x = D.786 (D.789, D.788); // [1]
if (x != 17) got...