avoid a bunch of checks in the likely display path

rep_any will get speculated `false` quite quickly, whereas checking if
the opcode is a string instruction will be costly no matter what. in the
rare case rep_any is true, i don't care how costly displaying the
instruction is - string instructions are relatively rare, and rep movs
is typically not more than one instance when it shows up.

1 files changed, 10 insertions, 10 deletions

diff --git a/src/long_mode/display.rs b/src/long_mode/display.rs
index 42d3683..5dac6cf 100644
--- a/src/long_mode/display.rs
+++ b/src/long_mode/display.rs
@@ -2244,18 +2244,18 @@ impl <T: fmt::Write, Color: fmt::Display, Y: YaxColors<Color>> ShowContextual<u6
             write!(out, "lock ")?;
         }
 
-        /*
-        if [Opcode::MOVS, Opcode::CMPS, Opcode::LODS, Opcode::STOS, Opcode::INS, Opcode::OUTS].contains(&self.opcode) {
-            // only a few of you actually use the prefix...
-            if self.prefixes.rep() {
-                write!(out, "rep ")?;
-            } else if self.prefixes.repz() {
-                write!(out, "repz ")?;
-            } else if self.prefixes.repnz() {
-                write!(out, "repnz ")?;
+        if self.prefixes.rep_any() {
+            if [Opcode::MOVS, Opcode::CMPS, Opcode::LODS, Opcode::STOS, Opcode::INS, Opcode::OUTS].contains(&self.opcode) {
+                // only a few of you actually use the prefix...
+                if self.prefixes.rep() {
+                    write!(out, "rep ")?;
+                } else if self.prefixes.repz() {
+                    write!(out, "repz ")?;
+                } else if self.prefixes.repnz() {
+                    write!(out, "repnz ")?;
+                }
             }
         }
-        */
 
         out.write_str(self.opcode.name())?;