-
Notifications
You must be signed in to change notification settings - Fork 171
Update to llvm 7.0 #22
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
Comments
Hello Marc, That is an excellent point. We are actually currently in the process of upgrading our compiler offline to using llvm 7.0. There is also an on going effort to remove/upstream the necessary patches. Our hopes are to target different Linux distributors in the future that require the latest llvm and clang. Stay tuned for these changes! |
Has this been completed? It seems llvm patches are still needed according to README. Please resolve, don't close/reopen this ticket. |
…f. (#22) This is required so debugger can set breakpoint at corresponding source lines. Co-authored-by: Pratik J Ashar <[email protected]>
…f. (#22) This is required so debugger can set breakpoint at corresponding source lines. Co-authored-by: Pratik J Ashar <[email protected]>
…f. (#22) This is required so debugger can set breakpoint at corresponding source lines.
…f. (#22) This is required so debugger can set breakpoint at corresponding source lines.
…f. (#22) This is required so debugger can set breakpoint at corresponding source lines.
…f. (#22) This is required so debugger can set breakpoint at corresponding source lines.
With llvm 7.0 out, we should update to the latest version of llvm. I also recommend upstreaming all the patches. This could allow one day to use system clang espically on linux
The text was updated successfully, but these errors were encountered: