Bug reports would be especially welcome here; we have an extremely
limited set of code bases to work from, and it turns out there are
some undocumented details that people have come to rely on, so it's
been difficult to determine just exactly what the capabilities are
supposed to be. Some of the known bugs are fixed in 3.5.
I'll file some reports shortly, but here are two things that
immediately spring to mind from this most recent project.
1. Using labels as branches in inline assembly causes multiple label
errors if the routines are called more than once in a larger routine.
2. CodeWarrior supports "nofralloc" as a way to avoid generating a
stack frame. We had code that would read the parameter in r3 and write
the result back r3. The ppc code generated by CodeWarrior was as
expected when used with nofralloc. With gcc, there was all sorts of
crazy glue that would unnecessarily copy the variable to the stack
frame, then to a local, then to r3, act on it, then copy r3 back to the
stack frame, and then finally back to r3.
--
Brad Oliver
email@hidden
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
