Skip to content

Should be optional warnings for common issues #5

@logic

Description

@logic

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions