-
Notifications
You must be signed in to change notification settings - Fork 101
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use dense FIR IDs across packages (#1296)
This change fixes three things: - It reduces the memory footprint by using dense FIR IDs across packages. This is accomplished by using a new lowerer instance for every package such that IDs for blocks, statements, expressions and pats are reset and start from zero. - It fixes a bug where the debugger would not honor a breakpoint if the statement that mapped to the breakpoint had the ID 0. - As a consequence of changing the way the FIR lowerer is used, the debugger would now randomly and inadvertently break into a core or standard library statement if the statement ID happened to be the same than the statement ID where a breakpoint is set in the user's code. This problem is also addressed by this change. This was done in collaboration with @swernli and @idavis. --------- Co-authored-by: Stefan J. Wernli <[email protected]>
- Loading branch information
Showing
8 changed files
with
317 additions
and
330 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.