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.

Sign up for GitHub

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

Jump to bottom

Import cmd/cover #2

Open
mdempsky opened this issue Apr 12, 2022 · 1 comment
Open

Import cmd/cover #2

mdempsky opened this issue Apr 12, 2022 · 1 comment

Comments

@mdempsky
Copy link
Collaborator

cmd/cover belongs under the amigo umbrella too, IMO.
@mdempsky
Copy link
Collaborator Author

mdempsky commented Apr 12, 2022 •
edited
Loading

More precisely, I think the amigo frontend should preserve enough information that it's trivial for compiler backends to insert appropriate coverage/fuzzing instrumentation as needed. My experience with go-fuzz and cmd/compile's native fuzzing support was that it was far simpler to just insert instrumentation within the compiler, than to force source-to-source transformation tools to rewrite code to stay spec-conforming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mdempsky