diff options
| author | Gabe Black <gblack@eecs.umich.edu> | 2009-08-08 17:23:19 -0700 |
|---|---|---|
| committer | Gabe Black <gblack@eecs.umich.edu> | 2009-08-08 17:23:19 -0700 |
| commit | 6e97feb8a546544172661bee2c75ce87ffbf33cf (patch) | |
| tree | d0095489a92597cc8798244f970b2001f4fabe2d /tests/long/10.mcf/ref/x86/linux | |
| parent | 7c606e3835bac328bad4dc13abfb770903f0a43f (diff) | |
| download | gem5-6e97feb8a546544172661bee2c75ce87ffbf33cf.tar.xz | |
X86: Make not taken conditional moves leave the destination alone. Adjust CMOVcc.
The manuals from both AMD and Intel say that when writing to a 32 bit
destination in 64 bit mode, the upper 32 bits of the register are filled with
zeros. They also both say that the CMOV instructions leave their destination
alone when their condition fails. Unfortunately, it seems that CMOV will zero
extend its destination register whether or not it was supposed to actually do
a move on both platforms. This seems to be the only case where this happens,
but it would be hard to say for sure.
Diffstat (limited to 'tests/long/10.mcf/ref/x86/linux')
0 files changed, 0 insertions, 0 deletions