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

Add support for LLVM 18 #662

Merged
merged 9 commits into from
Jun 22, 2024
Merged

Conversation

elliottslaughter
Copy link
Member

Currently passing all but 5 tests on macOS x86:

99% tests passed, 5 tests failed out of 550

Total Test time (real) =  52.38 sec

The following tests FAILED:
	 65 - class.t (SEGFAULT)
	 67 - class3.t (SEGFAULT)
	 68 - class4.t (SEGFAULT)
	 84 - constant2.t (SEGFAULT)
	 85 - constantinits.t (SEGFAULT)

@elliottslaughter elliottslaughter force-pushed the llvm18 branch 2 times, most recently from 7268c36 to f6a2064 Compare June 20, 2024 04:05
@elliottslaughter
Copy link
Member Author

The crashes all go away when I build LLVM and Terra with Address Sanitizer. I'm not quite sure what that means right now. I'm trying a couple more options to make sure this isn't the result of unrelated build flag changes. Unfortunately it's going to make debugging this a bit more difficult.

@elliottslaughter elliottslaughter mentioned this pull request Jun 20, 2024
@elliottslaughter
Copy link
Member Author

elliottslaughter commented Jun 22, 2024

The crashing tests were a result of not clearing out a function analysis manager when deleting a function. This also fixes #644 and probably #654.

@elliottslaughter
Copy link
Member Author

FreeBSD CI services are still down so I won't attempt to spin up an LLVM 18 test there.

@elliottslaughter elliottslaughter merged commit af046fb into terralang:master Jun 22, 2024
34 of 41 checks passed
@elliottslaughter elliottslaughter deleted the llvm18 branch June 22, 2024 03:30
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.

1 participant