edk2-libc: Add LoongArch64 support

[MarsDoge]

No description provided.

[MarsDoge]

Test Cases: OrderedCollectionTest

1. sh gentest.sh > input.txt
2. OrderedCollectionTest -i input.txt -o output.txt

[MarsDoge]

Hi @mdkinney @jpshivakavi @bexcran ,
would you mind reviewing this PR when you get a chance? Your feedback would be greatly appreciated. Thanks!

[jpshivakavi]

The build actions with GCC and VS tool chains are passing. It means that the changes are not breaking the existing things.

[mdkinney]

Do you want to add LOONGARCG to the GitHub actions to verify build? May require adding a build step in GCC build agent to just build StdLib.

[jpshivakavi]

@mdkinney it's a good suggestion, I will look into adding build action for building the stdlib - with MSFT Visual Studio, GCC and LoongArch64.

[MarsDoge]

Regarding Python interpreter support under AppPkg, it appears that the ARM platform is currently unsupported.
While I have verified the Lua interpreter on LoongArch, Python 3.6.8 requires additional SourceCode support, similar to ARM. Therefore, I suggest we first consider adding CI for the StdLib* build on the LoongArch platform.
This approach should not only apply to LoongArch CI but also be relevant for ARM CI setup.
Do you have any other suggestions or alternatives?

[jpshivakavi]

@MarsDoge Python 3.6.8 requires additional support for LoongArch64. That can be taken up as a separate effort. I am also of the pinion to setup a github action for StdLib covering the LoongArch64. @mdkinney mike is also suggesting the same.

@mdkinney is it ok if we setup a separate build action for the StdLib covering the X64, ARM and LoongArch64 with VS & GCC compilers for X64, and GCC compiler for ARM and LoongArch64. Let me know if you have any other thoughts.

[MarsDoge]

I tried to build a CI matrix to see if I could give you some reference.
You are welcome to correct me.: edk2-libc: add github workflow to build app efi with GCC

[mdkinney]

Yes. An independent CI job for StdLib sounds like a good idea since the support for StdLib and Python are not the same today

[MarsDoge]

@jpshivakavi Hello, it seems that there is a package (python3-distutils) issue with the current CI.
Please check and help to re-trigger CI, Tks !

[jpshivakavi]

@MarsDoge I have raised a pull request to fix the GCC build actions issue: #23

[MarsDoge]

@MarsDoge I have raised a pull request to fix the GCC build actions issue: #23

Before using containers to build CI environments, I also thought that fixed compiler versions were the only way.

[jpshivakavi]

@MarsDoge I believe the PR 21 contains all the changes in PR 20 and this may not be required to be merged if the PR 21 is processed. I think this PR can be closed without merging. Let me know if you have any concerns or questions.

[MarsDoge]

That's it, I will close this PR and only keep #21 open.