[WIP][SYCL] update lit test with the target #2586
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The lit test runs on a 32 bit windwos machine in downstream and causes qssertion failed: HT.getArch() == llvm::Triple::x86_64 && "Unsupported host architecture" inside Targets.cpp file. The patch updates this test to specify a target to fix the issue. Signed-off-by: Soumi Manna <soumi.manna@intel.com>
|
@erichkeane, the test still seems incorrect and does not solve the problem. I thought to share the patch with you to get some feedback on it. Thanks. |
smanna12
changed the title
|
Abandoned |
iclsrc
pushed a commit
that referenced
this pull request
Jun 6, 2024
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
jsji
pushed a commit
that referenced
this pull request
Jun 27, 2024
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
kbenzie
added a commit
to kbenzie/intel-llvm
that referenced
this pull request
Feb 17, 2025
…elease [DeviceASAN] Fix kernel release order
Chenyang-L
pushed a commit
that referenced
this pull request
Feb 18, 2025
[DeviceASAN] Fix kernel release order
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The lit test runs on a 32 bit windwos machine in downstream and causes
qssertion failed: HT.getArch() == llvm::Triple::x86_64 && "Unsupported host architecture"
inside Targets.cpp file.
The patch updates this test to specify a target to fix the issue.
Signed-off-by: Soumi Manna soumi.manna@intel.com