卧槽为什么执行
j pc + 0x110b4 spike 往 reg write log 里面记了一个 write to x0 with value 4 啊!要用 Spike,甚至还要处理这种灵车
.
do {
commit_log_reset(&processor);
pc = fetch.func(&processor, fetch.insn, state->pc);
if (pc & 1) {
// some weird Spike mechanics that we need to bypass.
switch (pc) {
case PC_SERIALIZE_BEFORE:
state->serialized = true;
break;
case PC_SERIALIZE_AFTER:
break;
default:
CHECK_S(false) << fmt::format("invalid pc (0x{:08X}).", pc);
}
} else
break;
} while (true);
state->pc = pc;
我发现 M2 MBA 开 Telegram 会议,对方分享了屏幕,这时候我切到别的 App 滚动屏幕(比如浏览网页)会有拖影和掉帧,但此时 CPU/GPU 占用并不高,难以理解。