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
Instruction 134 creates a new tuple and assigns images and labels to elements 0 and 1, respectively. But, I am losing track of these values later down the IR. I believe that the reason is that instruction 137 is incorrect. Specifically, there is no field of v270 whose value is stored in v304. In other words, I believe that there is a missing putfield instruction to store v304 in v270. That being said, the CAst printing is still able to track the variable names later down the IR:
But, I don't understand how, because the object stored v270 doesn't have a field whose value is v304; it's created in instruction 134 but never assigned. Either way, the dataflow analysis can't track it, so something is wrong here---either the IR or the dataflow analysis.
The text was updated successfully, but these errors were encountered:
khatchad
changed the title
Missing putfield in IR when traversing non-scalar iterables
Missing putfield in IR when traversing non-scalar iterable datasets
Jan 5, 2024
Consider the following Python code:
And corresponding IR:
From the above, consider the following snippet:
Instruction 134 creates a new tuple and assigns
images
andlabels
to elements 0 and 1, respectively. But, I am losing track of these values later down the IR. I believe that the reason is that instruction 137 is incorrect. Specifically, there is no field ofv270
whose value is stored inv304
. In other words, I believe that there is a missingputfield
instruction to storev304
inv270
. That being said, the CAst printing is still able to track the variable names later down the IR:But, I don't understand how, because the object stored
v270
doesn't have a field whose value isv304
; it's created in instruction 134 but never assigned. Either way, the dataflow analysis can't track it, so something is wrong here---either the IR or the dataflow analysis.The text was updated successfully, but these errors were encountered: