Open-sourcing CoreCLR MIPS64 Port

[theaoqi]

We're excited to announce that our CoreCLR MIPS64 Port has been open-sourced, and the initial commit has been pushed. The work is based on a commit nearly a year ago in dotnet/coreclr. We hope to implement a release version (3.0 or 3.1) first, and then to upgrade to upstream dotnet/runtime.

We are debugging priority1 tests in CoreCLR. More than 9500 tests have been passed according to our test method. The FlightFinder sample can work on MIPS64 now.

A gsvm/loongson-dotnet repository was created for general information, tools, downloads, etc., and further repositories may be created or forked if needed.

The work is still in progress. All contributions and suggestions are greatly welcomed. Please feel free to contact us.

Many thanks to Andy Ayers (@AndyAyersMS), Bruce Forstall (@BruceForstall), David Wrighton (@davidwrighton), Fei Peng (@fiigii), Jan Kotas (@jkotas), Jan Vorlicek (@janvorli), Maoni Stephens (@Maoni0), MeiChin-Tsai (@MeiChin-Tsai), and our great team!

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this issue. Please help me learn by adding exactly one area label.

[BruceForstall]

This is great to hear. Congratulations on the progress!

@richlander @dotnet/jit-contrib @jeffschwMSFT

[geffzhang]

Congratulations on reaching such a milestone

[mfjiang]

nice job !

[myFirstway]

It's exciting

[fiigii]

Great job! Congrat Loongson!

[janvorli]

Awesome! I was looking for this moment. Congratulations!

[maikebing]

Congratulations on reaching such a milestone

[RockNHawk]

Great job!

[lindexi]

Awesome

[theaoqi]

Awesome! I was looking for this moment. Congratulations!

Sorry, it was late ;)

[KatyushaScarlet]

Congratulations!

[maikebing]

When are you planning to merge into .net 5?

[theaoqi]

When are you planning to merge into .net 5?

We hope to begin the work of upgrading to master this year, but I cannot give an accurate time at present. Even if we finish all the work, I am not sure when dotnet/runtime will (or maybe already?) close the door for such a new port to stabilize .NET 5. .NET 6 is an LTS release. If possible, maybe we will try to merge into .NET 6. @BruceForstall , may I ask when is the deadline for merging such a big feature/port into .NET 5 and .NET 6?

[BruceForstall]

@theaoqi It's too late for such a large amount of work to go into .NET 5. The 'master' branch will become the .NET 6 branch probably in early September. Generally speaking, it would be better to try to start the process of upstreaming this work to 'master' early in the .NET 6 product cycle, so there is enough time to do that work, and when risk tolerance for change is higher than it is towards the end.

[jkotas]

Also, upstreaming of the delta that is this large will likely need to be broken into multiple smaller PRs to be manageable. It expect that it will take several months of effort to merge.

[theaoqi]

@BruceForstall @jkotas , thank you, you have helped to make it more clear for me!

[jason522008]

bravo loongson

[InCerryGit]

Congratulations! Great job!

[SofiaXu]

Great job!

[1426781227]

时刻关注着，dotnet发展！一起进入新的元年！

[jkotas]

@theaoqi @xiangzhai Do you have an estimate for when you will start upstreaming your changes to dotnet/runtime? Do you expect that you will start upstreaming the changes in next 6 months? We would like to make sure that we plan for it accordingly.

[theaoqi]

Thank you very much, @jkotas . I cannot be sure about this now. I will follow up on this, and let you know if there is any progress.

[happyNBB]

加油！！👍👍👍

[driver1998]

@theaoqi Port of the 3.1 release is generally available now, I guess it is time now for upstreaming? Hopefully it can catch up to .NET 6.

[woxihuanjia]

congratulations！

[wanghucheng66]

Great job!