-
Notifications
You must be signed in to change notification settings - Fork 182
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[XLS] Modernize to next-value nodes as soon as optimization starts
Since proc inlining is the only remaining pass that cannot work with next-value nodes, we let it convert the procs it's inlining to use next-state elements, then convert them back to next_value nodes at the end. This is the first step in our new plan for removing next-state element support: 1. (this change) Modernize to next-value nodes as soon as optimization starts, and let proc-inlining convert procs to next-state elements as needed 2. Switch all frontends to use next-value nodes natively 3. Make XLS IR verification reject nontrivial next-state elements, and remove the modernization pass from optimization 4. Switch proc-inlining from using next-state elements in procs to modeling them internally 5. Remove next-state element support from procs PiperOrigin-RevId: 706026298
- Loading branch information
1 parent
5e5e2e0
commit 82b203e
Showing
5 changed files
with
181 additions
and
49 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
Oops, something went wrong.