fixes - can self-compile with ORC! #74
Merged
Conversation
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
These fixes bring ORC to a point where `nlvm` can compile itself - there's a lot of bloat in the ORC code however, the end result being a binary that's 15% slower for now. ORC also breaks allocation elision, likely because the allocation functions have become too complex - this can perhaps be solved with some optimization pass reordering and/or selective early inlining, but it remains to be seen - first, excessive EH from range-checked pointer arithmetic must be addressed. * mark several C functions as `nounwind` to reduce EH bloat * better allocation / deallocation annotations * fix missing `wasMoved` calls
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These fixes bring ORC to a point where
nlvmcan compile itself - there's a lot of bloat in the ORC code however, the end result being a binary that's 15% slower for now.ORC also breaks allocation elision, likely because the allocation functions have become too complex - this can perhaps be solved with some optimization pass reordering and/or selective early inlining, but it remains to be seen - first, excessive EH from range-checked pointer arithmetic must be addressed.
nounwindto reduce EH bloatwasMovedcalls