Displaying 3 results from an estimated 3 matches for "linkabnorm".
2009 Jan 30
1
[LLVMdev] Hitting assertion, unsure why
...MENTS that explicitly handle
FrameIndexSDNode's as arguments. This leads me to believe that I
shouldn't have to handle this case and there is an error occurring
somewhere else and is showing up here.
My test case is fairly simple:
float func(float *a);
void test(float *positions)
{
float linkABNorm = positions[0];
float b = func(&linkABNorm);
positions[0] = b * linkABNorm;
}
float func(float *a)
{
*a = 10.0f;
return *a;
}
The problem is linked to taking the address of the stack variable and
passing it as a pointer to another function.
So, my questions are:
1) Is there anyth...
2009 Jan 28
0
[LLVMdev] Hitting assertion, unsure why
On Jan 27, 2009, at 3:54 PM, Villmow, Micah wrote:
> Ok, I've had time to track this down a little bit more and I seem to
> have found another case where it fails. This is occurring during
> Schedulur->EmitSchedule() in SelectionDAGISel.cpp:695. The problem
> seems
> to be that somehow the CopyToReg part of the switch statement in
> ScheduleDAG::EmitNode has a
2009 Jan 27
3
[LLVMdev] Hitting assertion, unsure why
Ok, I've had time to track this down a little bit more and I seem to
have found another case where it fails. This is occurring during
Schedulur->EmitSchedule() in SelectionDAGISel.cpp:695. The problem seems
to be that somehow the CopyToReg part of the switch statement in
ScheduleDAG::EmitNode has a FrameIndex as its second operand. This is
especially problematic because the code is either