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
There are situations where the logical data size of an instruction is smaller than the size of the symbol, such as struct initialization/copies.
#123 decides not to attempt to display a value for these types of data but this could be improved.
A better solution might go like this:
In the generic situation of the symbol size not matching the instruction "size" (the expected size of the data operated on by that instruction) then displaying it as bytes should work in any situation. If the symbol size is a multiple of the instruction "size" we could probably also interpret it as an array of that smaller type
The text was updated successfully, but these errors were encountered:
There are situations where the logical data size of an instruction is smaller than the size of the symbol, such as struct initialization/copies.
#123 decides not to attempt to display a value for these types of data but this could be improved.
A better solution might go like this:
In the generic situation of the symbol size not matching the instruction "size" (the expected size of the data operated on by that instruction) then displaying it as bytes should work in any situation. If the symbol size is a multiple of the instruction "size" we could probably also interpret it as an array of that smaller type
The text was updated successfully, but these errors were encountered: