71           "Number of post-load register values hardened");
452   // If we have loads being hardened and we've asked for call and ret edges to  in runOnMachineFunction()
555   LLVM_DEBUG(dbgs() << "Final speculative load hardened function:\n"; MF.dump();  in runOnMachineFunction()
1256 /// hardening those loads that are data dependent on a load with a hardened
1281     // loaded value hardened and all the loads that instead need their address  in tracePredStateThroughBlocksAndHarden()
1282     // hardened. During this walk we propagate load dependence for address  in tracePredStateThroughBlocksAndHarden()
1283     // hardened loads and also look for LFENCE to stop hardening wherever  in tracePredStateThroughBlocksAndHarden()
1286     // hardened at this point and if so, harden any remaining address registers  in tracePredStateThroughBlocksAndHarden()
1287     // as that often successfully re-uses hardened addresses and minimizes  in tracePredStateThroughBlocksAndHarden()
1291     // many loads value hardened even when some address register hardening would  in tracePredStateThroughBlocksAndHarden()
1359         // address registers, queue it up to be hardened post-load. Notably,  in tracePredStateThroughBlocksAndHarden()
1360         // even once hardened this won't introduce a useful dependency that  in tracePredStateThroughBlocksAndHarden()
1374         // operands as being address-hardened.  in tracePredStateThroughBlocksAndHarden()
1397         // Check if this is a load whose address needs to be hardened.  in tracePredStateThroughBlocksAndHarden()
1427               // If in sinking there was no instruction needing to be hardened,  in tracePredStateThroughBlocksAndHarden()
1440           // Mark the resulting hardened register as such so we don't re-harden.  in tracePredStateThroughBlocksAndHarden()
1446         // Check for an indirect call or branch that may need its input hardened  in tracePredStateThroughBlocksAndHarden()
1789           // some other post-load hardened instruction to it and it must itself  in sinkPostLoadHardenedInst()
1792                  "Data variant instruction being hardened!");  in sinkPostLoadHardenedInst()
1901 /// The new, hardened virtual register is returned. It will have the same
1952 /// Returns the newly hardened register.
1962   // the hardened value, create a dedicated new register that will only be used  in hardenPostLoad()
1967   // Now harden this register's value, getting a hardened reg that is safe to  in hardenPostLoad()
1974   // original def) with the hardened register.  in hardenPostLoad()
2203 /// will be adequately hardened already, we want to ensure that they are
2233   // instruction with an immediate operand which doesn't need to be hardened.  in hardenIndirectCallOrJumpInstr()
2242   // Try to lookup a hardened version of this register. We retain a reference  in hardenIndirectCallOrJumpInstr()
2243   // here as we want to update the map to track any newly computed hardened  in hardenIndirectCallOrJumpInstr()
2247   // If we don't have a hardened register yet, compute one. Otherwise, just use  in hardenIndirectCallOrJumpInstr()
2248   // the already hardened register.  in hardenIndirectCallOrJumpInstr()
2250   // FIXME: It is a little suspect that we use partially hardened registers that  in hardenIndirectCallOrJumpInstr()
2258   // Set the target operand to the hardened register.  in hardenIndirectCallOrJumpInstr()