-
Notifications
You must be signed in to change notification settings - Fork 90
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
Lit tests for cuda_add_cufft_to_target #1508
Lit tests for cuda_add_cufft_to_target #1508
Conversation
8cb6182
to
0d41070
Compare
0d41070
to
faab593
Compare
b3827d2
to
5f579db
Compare
2bebcec
to
55ee40c
Compare
Raised the behaviour test PR#573 for dpct_add_mkl_to_target |
55ee40c
to
a72ee1b
Compare
a72ee1b
to
295aa21
Compare
295aa21
to
55e6b78
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
059caf8
to
1f6a98c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you prepare a full CUDA test case in https://github.com/intel-sandbox/cmake_script_migration ?
1f6a98c
to
56f54b1
Compare
56f54b1
to
2894f17
Compare
2894f17
to
1fed6a7
Compare
Need rebase to solve the conflicting files |
Some of the upstream PRs are getting backported to the llvm_release_* branches, but those changes are never released. That prevents them from distributing as precompiled packages in various distributions like conda-forge and others. This PR targets this issue by creating automated workflow that is triggered once a month and generates automated releases for each such branch if there were changes since last release. This PR Adds workflow to generate releases every month from llvm_release_* branches in the format %llvm_major%.%llvm_minor%.%latest patch version +1%. For example: v18.1.1 v17.0.2 v17.0.1 v14.0.1 etc Release description matches as close as possible to current releases. The only difference is that llvm versions is represented by two numbers, instead of three, because it is impossible to recover exact version. You can check out example of generated versions here (there are few releases from the original proposal): https://github.com/ZzEeKkAa/SPIRV-LLVM-Translator/releases Workflow is set to be triggered once a month. It is also possible to trigger it manually from github actions UI. Merge process Merge the PR to main Trigger workflow manually Note There is no need to backport changes to all branches, since workflow dispatch on schedule basis can be performed only from main branch. Fixes: #1898 Fixes: #1508 Original commit: KhronosGroup/SPIRV-LLVM-Translator@63e89a9a268e5c2
Added lit test for cuda_add_cufft_to_target CMake macro