Skip to content
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

remove special case for the no-op first statement in fully_eliminated #51227

Merged
merged 2 commits into from
Sep 8, 2023

Conversation

aviatesk
Copy link
Member

@aviatesk aviatesk commented Sep 7, 2023

It looks like the special case is no longer needed. If this gets broken by future changes, I would like fix it or mark the test cases as broken.

It looks like the special case is no longer needed.
If this gets broken by future changes, we should fix it or mark the test
cases as `broken`.
test/compiler/irutils.jl Outdated Show resolved Hide resolved
test/compiler/irutils.jl Outdated Show resolved Hide resolved
@vtjnash
Copy link
Member

vtjnash commented Sep 7, 2023

It looks like maybe this was to make the test run correctly with --code-coverage?

@aviatesk
Copy link
Member Author

aviatesk commented Sep 7, 2023

I don't think so because this tweak was introduced since a change on the CFG transformation introduced spurious no-op statement (, which seems to have been fixed lately, xref: #50924), and AFAIU our compiler test suite isn't supposed to be run under --code-coverage enabled.

@vtjnash
Copy link
Member

vtjnash commented Sep 7, 2023

@aviatesk
Copy link
Member Author

aviatesk commented Sep 8, 2023

When we are going to fix the failures in coverage test runt, I'd like to add an explicit check of if coverage_enabled(...) within fully_eliminated.

@aviatesk aviatesk merged commit de297fa into master Sep 8, 2023
1 check passed
@aviatesk aviatesk deleted the avi/fix-fully_eliminated branch September 8, 2023 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants