[GlobalISel] Fix G_OR opcode after the addition of a TargetOpcode.

r275367 fixed G_ADD and G_BR, but not G_OR.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@275444 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/include/llvm/Target/TargetOpcodes.def b/include/llvm/Target/TargetOpcodes.def
index 5fe9cf781d3020b7c376ee7ff078f179fd9a9ea0..abab6c7a2a7c2aafcc7c46999ee706e10f226773 100644 (file)
--- a/include/llvm/Target/TargetOpcodes.def
+++ b/include/llvm/Target/TargetOpcodes.def
@@ -160,10 +160,10 @@ HANDLE_TARGET_OPCODE(G_ADD, 26)
 HANDLE_TARGET_OPCODE_MARKER(PRE_ISEL_GENERIC_OPCODE_START, G_ADD)
 
 /// Generic Bitwise-OR instruction.
-HANDLE_TARGET_OPCODE(G_OR, 25)
+HANDLE_TARGET_OPCODE(G_OR, 27)
 
 /// Generic BRANCH instruction. This is an unconditional branch.
-HANDLE_TARGET_OPCODE(G_BR, 27)
+HANDLE_TARGET_OPCODE(G_BR, 28)
 
 // TODO: Add more generic opcodes as we move along.