Skip to content

clean up exception use in backend #30

Closed

Description

@graydon

Some of the backend modules (asm, x86, ra, pe) use 'raise' or 'failwith' in a
way that escapes to the top level. This is undesirable; we have more structured
error handling in the middle-end, and can probably classify / manage such
errors a bit better. Though of course, nothing's ever "really" supposed to go
wrong in the backend...

Activity

  1. graydon commented on Jan 27, 2011

    @graydon
    ContributorAuthor

    WONTFIX (not required for bootstrapping)

  2. added a commit that references this issue on Dec 12, 2017
  3. added a commit that references this issue on Nov 29, 2018
  4. added a commit that references this issue on Sep 27, 2019
  5. added a commit that references this issue on Jun 30, 2020
    c7a0687
  6. added a commit that references this issue on Oct 1, 2021
  7. added 2 commits that reference this issue on Dec 4, 2023
  8. added a commit that references this issue on Dec 5, 2023
  9. added a commit that references this issue on Dec 5, 2023
  10. added a commit that references this issue on Jun 4, 2024
  11. added a commit that references this issue on Jul 10, 2024
  12. added a commit that references this issue on Jul 26, 2024
  13. added a commit that references this issue on Sep 8, 2025
  14. added 2 commits that reference this issue on Nov 11, 2025
  15. added a commit that references this issue on Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions