Add flag that will end compilation at or before a specified pass #9025
Comments
|
Sounds fine to me, and relatively simple to implement. I suspect there would be no objections to adding such a flag as a developer-only flag. |
|
I believe I have found where to implement |
|
Added the flag |
mppf
added a commit
that referenced
this issue
Apr 23, 2018
Add '--ignore-user-errors' and '--stop-after-pass' compiler flags [PR by @LouisJenkinsCS - thanks! tested/reviewed by @mppf] Introduced new flag, `--ignore-user-errors` which functions similar to `--ignore-errors` where it will continue compilation after discovering a user error, but unlike `--ignore-errors` it will stop at internal errors. The rationale for such a change is discussed in issue #9024. Also introduced is a new flag, `--stop-after-pass` which will cease compilation after the requested pass, which must match in name. If a pass is declared, it will check on each pass whether or not the names match and if so it will 'short-circuit' compilation to end early. The rationale for such a change is discussed in issue #9025 [Passed full local testing]
|
@LouisJenkinsCS: Can this issue be closed now that PR #9206 is merged? |
|
Yep, forgot about it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe there should be a flag that can be used to end compilation early. Currently there are flags to disable specific optimizations, to disable all optimization, and even to stop before code generation. A flag that stops compilation at a particular point helps compiler developers test up to a specific pass without having to wait for everything to finish or have to filter their results. It can also benefit developers that interact with the compiler as it provides more customization.
A proposed flag could be something like
--stop-after-pass <passname>.Edit:
Related issue: #9003
The text was updated successfully, but these errors were encountered: