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
It has been fixed partly? (see below excerpt from current source)
It is still surprising that the same iid will be used for different callbacks to the analysis. But at least analysis.js documents this now.
// avoid iid collision: make sure that iid+2 has the same source map as iid (@todo)varoprnd1=G(iid+2,base,offset,isComputed,true,false);returnfunction(oprnd2){// still possible to get iid collision with a mem operationvarval=B(iid,op,oprnd1,oprnd2,false,true,false);returnP(iid,base,offset,val,isComputed,true);};
The implementation of
A
in src/js/runtime/analysis.js is a bit odd.It uses the same iids for the calls to
G
,B
andP
:It should use different iids in the style of
M
:The text was updated successfully, but these errors were encountered: