Switch Legion to master branch and update #1622
Open
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.
This is preparation for the various Realm branches, getting Legion up to date to avoid future build complications.
flexflowbranch tomasterMy understanding is that the contents of Legion's
flexflowbranch are as follows:cfg_task_streamsto1by default-ll:streamsand no longer requires a branchLEGION_MAX_RETURN_SIZEBeyond this, Legion's
masterbranch has at least one critical feature for using Realm moving forward:dlopenthe librarylibcuda.soinstead of hard linking it, which makes test integration much easier.Therefore I think Legion's
masterbranch should be sufficient for all purposes moving forward and we should stop tracking a custom branch.This change is