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

[MLIR][OpenMP] Fix failing Lit tests #242

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

skatrak
Copy link
Member

@skatrak skatrak commented Jan 13, 2025

The omptarget-threadprivate-device-lowering.mlir test is updated with a valid target triple to prevent triggering an assertion during translation to LLVM IR.

The openmp-todo.mlir test is updated, since unsupported simd clauses no longer trigger errors but rather warnings. Messages triggered by these are also updated to avoid misleading users.

Verified

This commit was signed with the committer’s verified signature.
erikmd Erik Martin-Dorel
The omptarget-threadprivate-device-lowering.mlir test is updated with a valid
target triple to prevent triggering an assertion during translation to LLVM IR.

The openmp-todo.mlir test is updated, since unsupported simd clauses no longer
trigger errors but rather warnings. Messages triggered by these are also
updated to avoid misleading users.
@skatrak skatrak requested a review from ergawy January 13, 2025 11:24
Copy link

@ergawy ergawy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a small question.

@@ -525,7 +526,8 @@ static llvm::omp::ProcBindKind getProcBindKind(omp::ClauseProcBindKind kind) {
/// been mapped to LLVM IR values.
static LogicalResult
convertIgnoredWrapper(omp::LoopWrapperInterface opInst,
LLVM::ModuleTranslation &moduleTranslation) {
LLVM::ModuleTranslation &moduleTranslation,
const char *warningFmt) {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we do these changes upstream directly?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the moment at least, I don't think people upstream would be happy replacing errors with warnings when translating unsupported simd clauses. And there's not a need for adding a format string here unless we want to do something like that, so in my opinion this needs to remain downstream-only until simd clauses are all supported, at which point we could revert these changes.

@skatrak skatrak merged commit 31f64e5 into ROCm:amd-trunk-dev Jan 13, 2025
3 of 5 checks passed
@skatrak skatrak deleted the mlir-lit-fix branch January 13, 2025 12:32
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.

None yet

2 participants