You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Sail specification of CJALR, the link address is computed using setAddr, but in Flute, it is done by incrementing the offset of rg_pcc, which involves the fast representability check.
The text was updated successfully, but these errors were encountered:
I would have suspected that the link address would always have to be in bounds, since otherwise the instruction doesn't link. In-bounds capabilities shouldn't have a risk of being unrepresentable, I believe (even adding +4 to move onto the next instruction). If any of these assumptions aren't true then that would be concerning!
As reported by Dapeng Gao:
In the Sail specification of CJALR, the link address is computed using setAddr, but in Flute, it is done by incrementing the offset of rg_pcc, which involves the fast representability check.
The text was updated successfully, but these errors were encountered: