You are probably right, I've been away from this level of implementation for the last decade, but I was under the impression that if the branch target is fully known enough cycles in advance (as could be in this case if the jump table is in L1, if loading of ebp was pushed further back, and which IIRC LuaJIT2 does do) there is, in fact, no prediction involved. I'm likely wrong, though, and extrapolated the state of the art farther than where it actually is.
- Re: should `computedGoto` be always implied ? (ie make comp... doofenstein
- Re: should `computedGoto` be always implied ? (ie make... timothee
- Re: should `computedGoto` be always implied ? (ie ... juancarlospaco
- Re: should `computedGoto` be always implied ? ... timothee
- Re: should `computedGoto` be always implie... Araq
- Re: should `computedGoto` be always i... juancarlospaco
- Re: should `computedGoto` be alwa... Araq
- Re: should `computedGoto` be alwa... mratsim
- Re: should `computedGoto` be alwa... cumulonimbus
- Re: should `computedGoto` be alwa... mratsim
- Re: should `computedGoto` be alwa... cumulonimbus
