IS this project not being actively maintained?

Open
#440 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
compilers

Research direction

Start by reviewing the CUDA examples and CUDA test check mentioned in the issue, then reproduce the reported failures through the toolchain. The issue would be done when the expected path from a CUDA example to LLVM IR is documented or corrected and the CUDA tests have a clear outcome.

Written by the indexing model from the issue text.

Description

I looked at issues, and one person filed issue 74 in June. It is an issue I have seen. I added a comment with another failure pathway.

I would like to take one of your CUDA examples and put it through your toolchain and get out LLVM IR. Could you please demonstrate how you think this should work?

None of the CUDA tests pass, by the way, when I do the check after the build. I can provide more details if I think there is a point -- like someone actively monitoring these issues.

Dominant language
C++
Stars
624
Forks
170
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from llvm/Polygeist

All issues in llvm/Polygeist

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.