-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix bugs revealed by compiling alloc (#133)
This commit is an assortment of fixes for issues that were discovered by compiling the Rust `alloc` core library using the Hieratika compiler. It includes: - Fixes to constant building to account for the construction of explicitly-poisoned values. Note that these are _distinct_ from the FLO-level poisons which indicate static invalidity, as LLVM's poisons indicate dynamic invalidity. Poisons are safe to replace by valid values of the poisoned type, so this is what we do. - Handles additional cases in the building of constants to allow the compiler to support previously-unexpected cases. Doing this has required refactoring the auxiliary parsing infrastructure to aid in processing portions of the IR that Inkwell does not support well.
- Loading branch information
1 parent
c8f21e8
commit cf95ccb
Showing
18 changed files
with
1,808 additions
and
469 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.