platform.md: Add LoongArch ISA name la64v100

[cheese]

This adds the base ISA [1] of the LoongArch architecture to the platform lexicon.

Part of https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/1534

[1] https://loongson.github.io/LoongArch-Documentation/LoongArch-toolchain-conventions-EN.html

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[nanonyme]

RE: legal on arches, isn't a change like this so small that independent of CLA it should not really be problematic?

[EdSchouten]

Hi @nanonyme,
This is a fair question, whether the CLA should be required for this repository. We brought it up during today's remote execution working group meeting, but unfortunately nobody from Google attended it. I have already placed it on the agenda for next month's meeting. Will keep you posted!

[EricBurnett]

Apologies for missing the meeting today. I checked the CLA policy documentation internally and I don't see any provision for bypassing it on account of PR size. And logistically, I would not really expect so - a sequence of small changes could become a large change, which the auditing tooling would have to account for, etc...for auditability purposes if nothing else I think Google-run repos (including everything in bazelbuild) do require CLAs on all PRs. Sorry :(.

[EdSchouten]

I think the question we had in the monthly meeting was whether the CLA should apply to this repo to begin with, considering it merely captures a specification/standard, not an implementation.

[nanonyme]

Note that is now a repeating problem of remote execution ecosystem at large. No one who contributes ISA names (which I don't think are original work, they are just ISA names; if these are original work then they are original work of the creator of the ISA) into the documentation has signed Google CLA resulting in many cases the PR's dragging on for years. While clearly simplest option is @cheese simply signs CLA, this same problem seems to happen every time. Eg it took two years to get someone who had signed Google CLA to submit riscv64 ISA names. #176

[cheese]

I have signed Google CLA.