we've been building the FPR routines for ages (for compatibility with
system tools)..
This implements their use and also the GPRs - the latter makes an
appreciable reduction in code size,
the former is neutral for non-fp intensive code but, for example,
makes an appreciable reduction to the
On Oct 14, 2011, at 2:05 AM, Iain Sandoe wrote:
> This implements their use and also the GPRs - the latter makes an appreciable
> reduction in code size,
> OK for trunk?
Ok. Watch for problems with async stack walking (hitting sample in Activity
Monitor, or the walking done by CrashReporter)..
On 14 Oct 2011, at 10:29, Mike Stump wrote:
On Oct 14, 2011, at 2:05 AM, Iain Sandoe wrote:
This implements their use and also the GPRs - the latter makes an
appreciable reduction in code size,
OK for trunk?
Ok. Watch for problems with async stack walking (hitting sample in
Activity M
On Oct 28, 2011, at 3:40 AM, Iain Sandoe wrote:
> To test what you suggested I built some code that dropped down a few stack
> levels (with saves of FPR/GPR) and then either aborts or spins on a sleep.
Uhm, that's not enough, for async, you need to spawn threads that do the
interesting stuff in
