1. 19 5月, 2016 1 次提交
  2. 13 5月, 2016 15 次提交
  3. 23 3月, 2016 2 次提交
  4. 03 2月, 2016 1 次提交
  5. 29 1月, 2016 1 次提交
    • P
      exec: Clean up includes · 7b31bbc2
      Peter Maydell 提交于
      Clean up includes so that osdep.h is included first and headers
      which it implies are not included manually.
      
      This commit was created with scripts/clean-includes.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Message-id: 1453832250-766-4-git-send-email-peter.maydell@linaro.org
      7b31bbc2
  6. 06 11月, 2015 1 次提交
  7. 05 11月, 2015 1 次提交
  8. 04 11月, 2015 1 次提交
    • S
      cpu-exec: Fix compiler warning (-Werror=clobbered) · 0448f5f8
      Stefan Weil 提交于
      Reloading of local variables after sigsetjmp is only needed for some
      buggy compilers.
      
      The code which should reload these variables causes compiler warnings
      with gcc 4.7 when compiler optimizations are enabled:
      
      cpu-exec.c:204:15: error:
       variable ‘cpu’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Werror=clobbered]
      cpu-exec.c:207:15: error:
       variable ‘cc’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Werror=clobbered]
      cpu-exec.c:202:28: error:
       argument ‘env’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Werror=clobbered]
      
      Now this code is only used for compilers which need it
      (and gcc 4.5.x, x > 0 which does not need it but won't give warnings).
      
      There were bug reports for clang and gcc 4.5.0, while gcc 4.5.1
      was reported to work fine without the reload code. For clang it
      is not clear which versions are affected, so simply keep the status quo
      for all clang compilations. This can be improved later.
      Signed-off-by: NStefan Weil <sw@weilnetz.de>
      Message-Id: <1443266606-21400-1-git-send-email-sw@weilnetz.de>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      0448f5f8
  9. 20 10月, 2015 1 次提交
  10. 25 9月, 2015 1 次提交
  11. 16 9月, 2015 1 次提交
  12. 11 9月, 2015 1 次提交
  13. 09 9月, 2015 7 次提交
  14. 15 8月, 2015 1 次提交
    • P
      exec: drop cpu_can_do_io, just read cpu->can_do_io · 414b15c9
      Paolo Bonzini 提交于
      After commit 626cf8f4 (icount: set can_do_io outside TB execution,
      2014-12-08), can_do_io is set to 1 if not executing code.  It is
      no longer necessary to make this assumption in cpu_can_do_io.
      
      It is also possible to remove the use_icount test, simply by
      never setting cpu->can_do_io to 0 unless use_icount is true.
      
      With these changes cpu_can_do_io boils down to a read of
      cpu->can_do_io.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      414b15c9
  15. 06 8月, 2015 1 次提交
  16. 09 7月, 2015 1 次提交
  17. 26 6月, 2015 1 次提交
  18. 17 2月, 2015 2 次提交