1. 24 6月, 2016 1 次提交
    • A
      softfloat: Implement run-time-configurable meaning of signaling NaN bit · af39bc8c
      Aleksandar Markovic 提交于
      This patch modifies SoftFloat library so that it can be configured in
      run-time in relation to the meaning of signaling NaN bit, while, at the
      same time, strictly preserving its behavior on all existing platforms.
      
      Background:
      
      In floating-point calculations, there is a need for denoting undefined or
      unrepresentable values. This is achieved by defining certain floating-point
      numerical values to be NaNs (which stands for "not a number"). For additional
      reasons, virtually all modern floating-point unit implementations use two
      kinds of NaNs: quiet and signaling. The binary representations of these two
      kinds of NaNs, as a rule, differ only in one bit (that bit is, traditionally,
      the first bit of mantissa).
      
      Up to 2008, standards for floating-point did not specify all details about
      binary representation of NaNs. More specifically, the meaning of the bit
      that is used for distinguishing between signaling and quiet NaNs was not
      strictly prescribed. (IEEE 754-2008 was the first floating-point standard
      that defined that meaning clearly, see [1], p. 35) As a result, different
      platforms took different approaches, and that presented considerable
      challenge for multi-platform emulators like QEMU.
      
      Mips platform represents the most complex case among QEMU-supported
      platforms regarding signaling NaN bit. Up to the Release 6 of Mips
      architecture, "1" in signaling NaN bit denoted signaling NaN, which is
      opposite to IEEE 754-2008 standard. From Release 6 on, Mips architecture
      adopted IEEE standard prescription, and "0" denotes signaling NaN. On top of
      that, Mips architecture for SIMD (also known as MSA, or vector instructions)
      also specifies signaling bit in accordance to IEEE standard. MSA unit can be
      implemented with both pre-Release 6 and Release 6 main processor units.
      
      QEMU uses SoftFloat library to implement various floating-point-related
      instructions on all platforms. The current QEMU implementation allows for
      defining meaning of signaling NaN bit during build time, and is implemented
      via preprocessor macro called SNAN_BIT_IS_ONE.
      
      On the other hand, the change in this patch enables SoftFloat library to be
      configured in run-time. This configuration is meant to occur during CPU
      initialization, at the moment when it is definitely known what desired
      behavior for particular CPU (or any additional FPUs) is.
      
      The change is implemented so that it is consistent with existing
      implementation of similar cases. This means that structure float_status is
      used for passing the information about desired signaling NaN bit on each
      invocation of SoftFloat functions. The additional field in float_status is
      called snan_bit_is_one, which supersedes macro SNAN_BIT_IS_ONE.
      
      IMPORTANT:
      
      This change is not meant to create any change in emulator behavior or
      functionality on any platform. It just provides the means for SoftFloat
      library to be used in a more flexible way - in other words, it will just
      prepare SoftFloat library for usage related to Mips platform and its
      specifics regarding signaling bit meaning, which is done in some of
      subsequent patches from this series.
      
      Further break down of changes:
      
        1) Added field snan_bit_is_one to the structure float_status, and
           correspondent setter function set_snan_bit_is_one().
      
        2) Constants <float16|float32|float64|floatx80|float128>_default_nan
           (used both internally and externally) converted to functions
           <float16|float32|float64|floatx80|float128>_default_nan(float_status*).
           This is necessary since they are dependent on signaling bit meaning.
           At the same time, for the sake of code cleanup and simplicity, constants
           <floatx80|float128>_default_nan_<low|high> (used only internally within
           SoftFloat library) are removed, as not needed.
      
        3) Added a float_status* argument to SoftFloat library functions
           XXX_is_quiet_nan(XXX a_), XXX_is_signaling_nan(XXX a_),
           XXX_maybe_silence_nan(XXX a_). This argument must be present in
           order to enable correct invocation of new version of functions
           XXX_default_nan(). (XXX is <float16|float32|float64|floatx80|float128>
           here)
      
        4) Updated code for all platforms to reflect changes in SoftFloat library.
           This change is twofolds: it includes modifications of SoftFloat library
           functions invocations, and an addition of invocation of function
           set_snan_bit_is_one() during CPU initialization, with arguments that
           are appropriate for each particular platform. It was established that
           all platforms zero their main CPU data structures, so snan_bit_is_one(0)
           in appropriate places is not added, as it is not needed.
      
      [1] "IEEE Standard for Floating-Point Arithmetic",
          IEEE Computer Society, August 29, 2008.
      Signed-off-by: NThomas Schwinge <thomas@codesourcery.com>
      Signed-off-by: NMaciej W. Rozycki <macro@codesourcery.com>
      Signed-off-by: NAleksandar Markovic <aleksandar.markovic@imgtec.com>
      Tested-by: NBastian Koppelmann <kbastian@mail.uni-paderborn.de>
      Reviewed-by: NLeon Alrae <leon.alrae@imgtec.com>
      Tested-by: NLeon Alrae <leon.alrae@imgtec.com>
      Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
      [leon.alrae@imgtec.com:
       * cherry-picked 2 chunks from patch #2 to fix compilation warnings]
      Signed-off-by: NLeon Alrae <leon.alrae@imgtec.com>
      af39bc8c
  2. 19 5月, 2016 1 次提交
  3. 21 1月, 2016 1 次提交
  4. 19 1月, 2016 1 次提交
  5. 17 12月, 2015 1 次提交
    • A
      target-arm: kvm - re-inject guest debug exceptions · 34c45d53
      Alex Bennée 提交于
      If we can't find details for the debug exception in our debug state
      then we can assume the exception is due to debugging inside the guest.
      To inject the exception into the guest state we re-use the TCG exception
      code (do_interrupt).
      
      However while guest debugging is in effect we currently can't handle the
      guest using single step as we will keep trapping to back to userspace.
      GDB makes heavy use of single-step behind the scenes which effectively
      means the guest's ability to debug itself is disabled while it is being
      debugged.
      Signed-off-by: NAlex Bennée <alex.bennee@linaro.org>
      Message-id: 1449599553-24713-6-git-send-email-alex.bennee@linaro.org
      [PMM: Fixed a few typos in comments and commit message]
      Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      34c45d53
  6. 15 9月, 2015 1 次提交
  7. 09 9月, 2015 1 次提交
  8. 07 9月, 2015 1 次提交
  9. 26 6月, 2015 1 次提交
  10. 29 5月, 2015 1 次提交
  11. 02 4月, 2015 1 次提交
  12. 13 2月, 2015 1 次提交
  13. 05 2月, 2015 2 次提交
  14. 24 10月, 2014 3 次提交
  15. 30 9月, 2014 6 次提交
  16. 04 8月, 2014 2 次提交
  17. 09 6月, 2014 2 次提交
  18. 29 5月, 2014 1 次提交
  19. 28 5月, 2014 4 次提交
  20. 18 4月, 2014 1 次提交
  21. 18 3月, 2014 5 次提交
  22. 20 2月, 2014 2 次提交