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

Should be optional warnings for common issues #5

Open
logic opened this issue Dec 9, 2017 · 0 comments
Open

Should be optional warnings for common issues #5

logic opened this issue Dec 9, 2017 · 0 comments

Comments

@logic
Copy link
Owner

logic commented Dec 9, 2017

A common problem is branch instructions with ambiguous targets (JSR is register-relative, and we don't always have strict confidence about the value of a register). It would be useful to have a CLI argument that calls out issues like this, where we know something isn't right but don't know what to do about it, so that the user might be able to figure something out.

Something like --warn is probably good enough to start with (we could add levels if we start winding up with more warning conditions, but if this is all we have off the bat, no sense making it complicated right off the bat).

Alternatively, we could just output warnings to stderr by default, and not worry about a CLI flag at all.

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

No branches or pull requests

1 participant