Limitations

Current limitations of the SPARCv8 target include:

  • The wrpsr instruction is effective immediately. The up to three nops, needed in real code serves no purpose in the emulator. Thus if nops are omitted you will not detect this on the emulator at present.

  • Floating point traps are direct and not deferred. This is the correct behaviour for the AT697F, but may not be correct for other chips.

  • Timing effects due to super-scalar execution is not simulated. Again, this is correct behaviour for the AT697F.

  • Operator dependant timing effects (especially noticeable in the FPU) are not simulated. Timing for instructions is static and uses the documented typical values.

  • The LEON2 model takes FPU timings from the ERC32 as no known documentation about the costs on the MEIKO FPU is available. The only known data for the MEIKO is in the same magnitude as the ERC32 FPU (which is not MEIKO), hence we assume that the ERC32 timings are roughly correct for the LEON2.

  • The FPU model is based on the SPARCv8 standard, and follows the SPARCv8 recommendations for NaN-propagation. If the SPARCv8 you emulate use an FPU that is not compliant with the SPARCv8 NaN propagation recommendations, there may be slight deviation in results. If you need an FPU core that follows different rules, please contact Terma.

  • The cache interface do not support line locking at present.

  • The SVT trapping model is not supported at present