Iob supertag, mergedb improvement, groupmask util #458
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
mcmasterg
changed the title
Signed-off-by: Tomasz Michalak <[email protected]>
Signed-off-by: John McMaster <[email protected]>
Signed-off-by: John McMaster <[email protected]>
Signed-off-by: John McMaster <[email protected]>
Signed-off-by: John McMaster <[email protected]>
Signed-off-by: John McMaster <[email protected]>
mcmasterg
force-pushed
the
iob_supertag
branch
from
7bf44cd to
d0d6778
Compare
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.
Experimental fuzzer to create some large IOB tags encompassing many other tags. There is an outstanding issue still under investigation (possibly related to segprint), but it seems to at least mostly work.
Also fixes #347 by adding a groupmask utility. This isn't well integrated into the build system, but the building block is there if we want to start deploying it more
Also changed mergedb to deal with conflicts much more intelligently. Now that we are aware which entry is new, new entries are given precedence when pushing to the db. A warning is omitted when overriding an old entry. For development, you can "MERGEDB_STRICT=0 make pushdb" if you want to force the merge and take the new value