- 04 Dec, 2009 1 commit
-
-
ROOL authored
Detail: This change fixes ticket #225 (post-indexed LDFD via r13 sometimes reading corrupted values). It also fixes LDFS, LDFP and LDFE, which suffered from the same problem. The post-increment was done too early, which left the values to be loaded unprotected below r13_svc, so interrupt routines dropping into SVC mode would trample over them. With my fix, the values are loaded from the stack while interrupts are still disabled, which protects them against corruption. Admin: Tested on various RISC OS platforms. Changes by: Martin Wuerthner Version 4.28. Tagged as 'FPASC-4_28'
-
- 10 May, 2009 1 commit
-
-
Ben Avison authored
Detail: FPASC is still distributed as a set of pre-built binaries, selected on the basis of the Machine build variable. Now that the OMAP3 port has switched to using Machine="CortexA8", we need a new pre-built binary. This one is copied from the Tungsten binary, as both can use a CELM build variant. Admin: Not yet tested. Retagged as FPASC-4_27 as the addition of this file will not affect any builds using the existing tag.
-
- 30 Apr, 2009 1 commit
-
-
ROOL authored
Detail: We're still waiting for clearance for ARM to release the sources to FPEmulator/FPASC. The sources can build many different variants depending upon which target machine(s) are required and which OS facilities are available, but for now we're bodging this binary-only release to support two pre-built binaries (rather than the Tungsten-only build previously offered). These are: * M-variant, suitable for machines with or without hardware FPA, and where only ARMv3 instructions are used * CELM-variant, suitable only for machines without hardware FPA, and using ARMv4 and ARMv5 instructions Both variants assume they are running on an Ursula kernel or later. Admin: Not tested, but should be a low-risk change. Version 4.27. Tagged as 'FPASC-4_27'
-
- 03 Dec, 2008 1 commit
-
-
Ben Avison authored
This is the result of executing the BBE build phase on a complete Tungsten ROM build. It may be linked into any other compatible ROM builds in the same way as if the source was available, but obviously it cannot be studied or improved upon in its current form, and it is not portable to any incompatible architecture variants or ABIs. It is hoped that in future this will be replaced by a full source release.
-