-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fuzzgen: Always generate reachable blocks #5034
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I used all my brain today on reviewing the egraphs PR and can't give this the attention I'd like to. @cfallin, could you verify that this implementation of CFG generation makes sense to you, and merge this if so?
Certainly; I owe you several brain refills for that review, thanks! I'll take a look at this PR tomorrow. |
Thanks @jameysharp! Co-authored-by: Jamey Sharp <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great work as always -- thanks so much!
A thought below on a way to possibly remove the boxed closures; but otherwise, all good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with updates; thanks a bunch!
👋 Hey,
This PR alters fuzzgen to always generate reachable blocks. See #5022 for context.
We do this by making sure that whenever we insert terminators at least one of the edges points to the next block.
Another thing this PR does is separate the CFG construction from block terminator insertion.
This fuzzed ok individually, but I'm now also testing with #5020 on top to see if it finds anything else.
cc: @jameysharp