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
The output of the dbg functionality can be far better, with the wealth of info that Finwë has. In particular, it should know what the types of the data on the stack, and format that data accordingly (while also printing the raw values just in case that's what's wanted.
This would necessitate keeping track of all that information during compile time. To prevent memory usage from blowing up, we could stick a special flag on dbg function that makes the caller store this information for each node during analysis rather than throwing it away: #intrinsics-store-analysis-data.
To be clear, this data would not be emitted in the ROM.
Or... maybe it could be emitted in the upcoming .finwe_syms file? Then we'd have to store it for each function anyway...
The text was updated successfully, but these errors were encountered:
The output of the
dbg
functionality can be far better, with the wealth of info that Finwë has. In particular, it should know what the types of the data on the stack, and format that data accordingly (while also printing the raw values just in case that's what's wanted.This would necessitate keeping track of all that information during compile time. To prevent memory usage from blowing up, we could stick a special flag on
dbg
function that makes the caller store this information for each node during analysis rather than throwing it away:#intrinsics-store-analysis-data
.To be clear, this data would not be emitted in the ROM.
Or... maybe it could be emitted in the upcoming
.finwe_syms
file? Then we'd have to store it for each function anyway...The text was updated successfully, but these errors were encountered: