cheriot is not a CPU name

[davidchisnall]

The back end is currently using CPU == "cheriot" in a few places. We should be looking for Xcheri and Xcheriot so that eventually we can look for Zcheri and Xcheriotv{version number}.

[v01dXYZ]

Hello,

I'm a junior dev which tries to learn about compilers. I'm interested into contributing to your LLVM fork as contributing to LLVM directly requires quite a lot of patience and I think it would be easier for me if I receive feedback more frequently.

Is this issue still relevant ?

[davidchisnall]

Hi! It is, but @resistor is currently in the process of updating from LLVM 13 to 17, which will touch a lot of this code and would cause some merge pain for you. I think #34 might be easy to do and then rebase on the new branch, if you're interested in working on clang, as might #4. Alternatively, I hope the merge to 17 will be done soon and then this should be a good first issue.

[resistor]

@v01dXYZ I have a patch queued up for after LLVM 17 lands, which will add "riscv32cheriot" as a sub-architecture to the TargetTriple. Once that's in, we should migrate most or all of the instances of CPU == "cheriot' to check the sub-architecture of the triple instead.

[resistor]

First part of this is in #63