summaryrefslogtreecommitdiff
path: root/Source/Core/InputCommon/ControllerInterface/evdev
diff options
context:
space:
mode:
authorLioncash <mathew1800@gmail.com>2018-06-01 18:55:26 -0400
committerLioncash <mathew1800@gmail.com>2018-06-01 20:21:09 -0400
commita08ad82ace064f961b13369c96a0f3b48ca7ca5c (patch)
tree1d535eb99039a7a8d673b7ae143a95fb83500bc5 /Source/Core/InputCommon/ControllerInterface/evdev
parentfcae27981acce6f1ccbc0cfa5163416385830c5e (diff)
Interpreter_FloatingPoint: Don't store to destination in fres if VE or ZE is set and a relevant exception occurs
In the PowerPC Microprocessor Family: The Programming Environments Manual for 32 and 64-bit Microprocessors, in section 3.3.6.1, Table 3-12 lists what should occur if an invalid operation exception occurs in situations where VE is set and when VE is not set. In the case where VE is set, it lists the frD as "Unchanged". It also lists the FPRF flags as "Unchanged". Further down in Table 3-13, the listings for what should occur when zero divide exceptions occur is listed, both for when ZE is set, and when it isn't. When ZE is set, it lists frD as "Unchanged". It also lists the FPRF flags as "Unchanged" as well. This also alters the code so that we don't even calculate the result if we don't need to compute it, making it a little bit less wasteful.
Diffstat (limited to 'Source/Core/InputCommon/ControllerInterface/evdev')
0 files changed, 0 insertions, 0 deletions