@lorentey any progress?

Did you intentionally target this PR on the main branch, rather than on the release/1.1 series?

@lorentey in the other parts of the swift project I have always submitted PR's to the main branch and then cherrypicked to release/ branches as needed. Is your workflow different for this project?
Thanks.

Yes. Changes in this repository need to land in the earliest release branch that wants to ship them.

The project maintainer then merges (not cherry-picks, merges) them to downstream branches as needed.

This is explained in the README.

@lorentey, apologies, I should have read the README more closely.
Yes this should be targeting the release/1.1 branch.
Can you make this change.
Thanks.

@futurejones Do you no longer need this change, or were you just unable to retarget it on the release/1.1 branch?

@lorentey I don't have write access to this repository so I can't edit and retarget the PR target branch.
That is why I asked you to make the change

Yes this should be targeting the release/1.1 branch.
Can you make this change.
Thanks.

After waiting for nearly 2 months with no response I decided to close the PR rather get stuck in a frustrating cycle of pinging and getting no response.

This is what I have been experiencing with other PR's that I have been trying to get approved in several other swift sub projects.

Whether or not this PR gets approved and merged is not for my need or benefit, it was to improve the swift project support for everyone.

anyway, thanks for responding.

@futurejones I see. I can rebase your commit on top of release/1.1 for you if you want. I have no way to verify that the result will work though, and I strongly suspect the CMake change is not going to be enough.

The swift-collections codebase includes a handful of cases where Swift code is conditional on the target architecture, and none of those know about riscv64 as a possibility. To properly support 64-bit RISC-V, I expect these will need to be updated, preferably by refactoring them to use the new _pointerBitWidth condition (we generally have these because we needed to know the size of pointers).