Merging P2LLVM into upstream: what we need
I'm getting to a point with p2llvm that I want to submit the target in the LLVM codebase to the upstream repo, so we can regularly take advantage of updates to LLVM and clang without it constantly breaking the target code. I sent an email to the LLVM folks with a series of questions and requirements, which I've linked below. There's quite a few things to do still in terms of testing and cleanup, but one major one that is needed is "active community support". I intend to keep supporting the project, but it will be difficult to do it entirely alone, and the llvm team would also want more than one person who is able to support it, run and maintain tests, etc.
Is anyone willing to sign up to be a code owner for this effort? My hope is that the effort is minimal, and I will still take the bulk of the work, but having more than one person the llvm team can reach out to would be good for getting this supported long term.
My hope is that if we get this submitted into the upstream repo, we can have a stable, modern, and complete C++ toolchain option for P2, the community can put most effort into developing libraries and hardware support code, rather than trying to solve compiler problems. There's still plenty of features I want to add, but for the most part, the target is working and you can compile most programs you would want.
Discussion with LLVM: https://groups.google.com/g/llvm-dev/c/QJgTO9vBIqU