| commit | 111d7f4a69751d333bac32526cd252add6b071d3 | |
| author | Aurelien Jarno <aurelien@aurel32.net> | |
| Wed, 3 Jun 2015 21:09:41 +0000 (3 23:09 +0200) | ||
| committer | Alexander Graf <agraf@suse.de> | |
| Thu, 4 Jun 2015 23:37:58 +0000 (5 01:37 +0200) | ||
| tree | ed59dd7680c03dcd29905eba1dbad1a26cd4620f | treesnapshot (tar.gz zip) |
| parent | a1c7610a68795d66249c25166220324d4d0b9289 | commitdiff |
target-s390x: fix exception for invalid operation code
When an operation code is not recognized (ie invalid instruction) an
operation exception should be generated instead of a specification
exception. The latter is for valid opcode, with invalid operands or
modifiers.
This give a very basic GDB support in the guest, as it uses the invalid
opcode 0x0001 to generate a trap.
Reviewed-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Signed-off-by: Alexander Graf <agraf@suse.de>
When an operation code is not recognized (ie invalid instruction) an
operation exception should be generated instead of a specification
exception. The latter is for valid opcode, with invalid operands or
modifiers.
This give a very basic GDB support in the guest, as it uses the invalid
opcode 0x0001 to generate a trap.
Reviewed-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Signed-off-by: Alexander Graf <agraf@suse.de>
| target-s390x/translate.c | diffblobblamehistory |