Skip to content

[CIR] Introduce a new dir in tests for known crashes to fix #1243

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

Merged

Conversation

lanza
Copy link
Member

@lanza lanza commented Dec 19, 2024

We figure it would be nice to have a common place with all our known
crashes that is tracked by git and is actively verified whether or not
we can now support the crashes by lit. It can act as our source of truth
for known failures and also being potential good first tasks for new
developers.

Add a simple test case of a known crash that involves copying a struct
in a catch.

Created using spr 1.3.5
Created using spr 1.3.5
@lanza
Copy link
Member Author

lanza commented Dec 19, 2024

@bcardosolopes Any clue why this doesn't crash without -fexceptions? Where does the cirgen behavior diverge based only on the -fexceptions` flag?

@bcardosolopes
Copy link
Member

Any clue why this doesn't crash without -fexceptions? Where does the cirgen behavior diverge based only on the -fexceptions` flag?

Not sure, answering that question is equivalent to chasing/fixing the bug in hand.

@lanza lanza merged commit 232db8c into main Dec 20, 2024
6 checks passed
@lanza lanza deleted the spr/lanza/cir-introduce-a-new-dir-in-tests-for-known-crashes-to-fix branch December 20, 2024 04:50
lanza added a commit that referenced this pull request Mar 18, 2025
We figure it would be nice to have a common place with all our known
crashes that is tracked by git and is actively verified whether or not
we can now support the crashes by lit. It can act as our source of truth
for known failures and also being potential good first tasks for new
developers.

Add a simple test case of a known crash that involves copying a struct
in a catch.

Reviewers: smeenai, bcardosolopes

Reviewed By: bcardosolopes

Pull Request: #1243
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

Successfully merging this pull request may close these issues.

2 participants