From 38cc5478bca0f858dbe69076ce033f8563b5d2e9 Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Mon, 27 May 2019 20:50:02 +0200 Subject: [PATCH] host_amd64_defs.c don't initialize opc and subopc_imm in emit_AMD64Instr. In the case of Ain_SseShiftN we first assign zero to opc and subopc_imm before handling the various subops. But since we will (and must) always assign a valid value to opc and subopc_imm we might get a compiler warning about the values never being read before storing a different value. So explicitly don't assign a value. Then the compiler will warn if we would ever forget to assign it a value value later on before using it. --- VEX/priv/host_amd64_defs.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/VEX/priv/host_amd64_defs.c b/VEX/priv/host_amd64_defs.c index f022b4fa46..29127c1258 100644 --- a/VEX/priv/host_amd64_defs.c +++ b/VEX/priv/host_amd64_defs.c @@ -3952,8 +3952,6 @@ Int emit_AMD64Instr ( /*MB_MOD*/Bool* is_profInc, goto done; case Ain_SseShiftN: { - opc = 0; // invalid - subopc_imm = 0; // invalid UInt limit = 0; UInt shiftImm = i->Ain.SseShiftN.shiftBits; switch (i->Ain.SseShiftN.op) { -- 2.47.2