The tradeoff is complexity. The microcode must be carefully arranged so that the instructions in delay slots are either useful setup for both paths, or at least harmless if the redirect fires. Not every case is as clean as RETF. When a PLA redirect interrupts an LCALL, the return address is already pushed onto the microcode call stack (yes, the 386 has a microcode call stack) -- the redirected code must account for this stale entry. When multiple protection tests overlap, or when a redirect fires during a delay slot of another jump, the control flow becomes hard to reason about. During the FPGA core implementation, protection delay slot interactions were consistently the most difficult bugs to track down.
* 时间O(n) 空间O(n)（理论最优，无冗余计算/存储）。91视频对此有专业解读
bucketArr[k + 1] = key;。关于这个话题，服务器推荐提供了深入分析
Mandatory registration creates friction and barriers to entry, particularly for: