Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Xing Lin
qemu
Commits
82c7e2a4
Commit
82c7e2a4
authored
Jan 04, 2004
by
bellard
Browse files
update
git-svn-id:
svn://svn.savannah.nongnu.org/qemu/trunk@501
c046a42c-6fe2-441c-8c8c-71466251a162
parent
546cdbd7
Changes
2
Hide whitespace changes
Inline
Side-by-side
Makefile
View file @
82c7e2a4
...
@@ -46,7 +46,7 @@ install: all
...
@@ -46,7 +46,7 @@ install: all
done
done
# various test targets
# various test targets
test speed
:
all
test speed
test2
:
all
make
-C
tests
$@
make
-C
tests
$@
TAGS
:
TAGS
:
...
...
TODO
View file @
82c7e2a4
- user/kernel PUSHL/POPL in helper.c
- keyboard output buffer filling timing emulation
- verify tb_flush() with a20 and TLBs
- cmos clock update and timers
- test ldt limit < 7 ?
- tests for each target CPU
- tests for each target CPU
- ppc qemu test
- optimize FPU operations (evaluate x87 stack pointer statically) and
- optimize FPU operations (evaluate x87 stack pointer statically) and
fix cr0.TS emulation
fix cr0.TS emulation
- fix some 16 bit sp push/pop overflow
- fix some 16 bit sp push/pop overflow
(pusha/popa, lcall lret)
- sysenter/sysexit emulation
- sysenter/sysexit emulation
- finish segment ops (call far, ret far, load_seg suppressed)
- fix CCOP optimisation
- fix CCOP optimisation
- fix all remaining thread lock issues (must put TBs in a specific invalid
- fix all remaining thread lock issues (must put TBs in a specific invalid
state, find a solution for tb_flush()).
state, find a solution for tb_flush()).
- cpu loop optimisation (optimise ret case as the cpu state does not change)
- fix arm fpu rounding (at least for float->integer conversions)
- fix arm fpu rounding (at least for float->integer conversions)
lower priority:
lower priority:
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment