-
Notifications
You must be signed in to change notification settings - Fork 92
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
printer: ensure compatibility with asmfmt #8
Comments
mmcloughlin
added a commit
that referenced
this issue
Jan 11, 2019
mmcloughlin
added a commit
that referenced
this issue
Jan 11, 2019
Run asmfmt suring linting and confirm git repository isn't dirty. This introduces a developer tools dependency on asmfmt, but not a runtime dependency. Updates #8
mmcloughlin
added a commit
that referenced
this issue
Jan 11, 2019
Fixed by 27cea3b |
Based on 3ca82be I think we have a mismatch with comments ahead of labels. But there seems to be a special case when there is a comment above and below a label? Needs investigation. |
I think |
mmcloughlin
added a commit
that referenced
this issue
Jan 28, 2020
For compatibility with `asmfmt` Updates #8
mmcloughlin
added a commit
that referenced
this issue
Jan 28, 2020
Adds a regression test based on klauspost/compress#186. This necessitated some related changes: * Mark "RET" as a terminal instruction * printer refactor to maintain compatibility with asmfmt * Tweaks to other regression tests to ensure they are run correctly in CI Updates #100 #65 #8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
klauspost/asmfmt is the de facto standard for Go assembly formatting. It would be good to produce output that conforms to
asmfmt
.I have a preference for avoiding non-Go dependencies (stdlib and sub-repos only). Therefore:
asmfmt
explicitly, that would be preferred. This may actually be possible since (at the time of writing) many of theasmfmt
rules simply wouldn't apply toavo
output.asmfmt
are too complicated, then we can accept the additional dependency.Either way, it would be good to have a check in CI to confirm that all generated files are formatted correctly. Something like
find . -name '*.s' | xargs asmfmt -w
and check the git repo is clean.The text was updated successfully, but these errors were encountered: