On Dec 6, 2016, at 4:41 PM, Greg Parker wrote:
On Dec 6, 2016, at 7:27 AM, G 3 wrote:
I'm working on a program that calls PowerPC assembly floating
point instructions from C. It would have calls like this:
double inputA, inputB, answer;
asm volatile("fadd %0, %1, %2" : "=f" (answer) : "
> On Dec 6, 2016, at 7:27 AM, G 3 wrote:
>
> I'm working on a program that calls PowerPC assembly floating point
> instructions from C. It would have calls like this:
>
> double inputA, inputB, answer;
> asm volatile("fadd %0, %1, %2" : "=f" (answer) : "f" (inputA), "f" (inputB));
> // answ
> On 6 Dec 2016, at 15:27, G 3 wrote:
>
> Is there a way to fix this problem?
>
Have you tried lowering the release build optimisation level to match the level
used for debug build?.
It might get you on the right track.
J
___
Cocoa-dev mailing li
I'm working on a program that calls PowerPC assembly floating point
instructions from C. It would have calls like this:
double inputA, inputB, answer;
asm volatile("fadd %0, %1, %2" : "=f" (answer) : "f" (inputA),
"f" (inputB)); // answer = inputA + inputB
The odd thing is it only works i
