Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev.loong64: create dev branch for the loong64 port #47569

Closed
xen0n opened this issue Aug 6, 2021 · 3 comments
Closed

dev.loong64: create dev branch for the loong64 port #47569

xen0n opened this issue Aug 6, 2021 · 3 comments
Labels
FrozenDueToAge NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made.

Comments

@xen0n
Copy link
Member

xen0n commented Aug 6, 2021

Upstream work to bring up the LoongArch architecture is still at an early stage; many aspects of C & kernel ABIs haven't finalized yet, so it's unlikely for the loong64 Go port to be finished in the 1.18 development cycle from an upstream perspective.

Because of this, and according to the Porting Policy (a port must be finished in the cycle it was started or will be removed), we (the LoongArch developer community & compiler engineers from the Loongson Corporation) are requesting the creation of a dev.loong64 branch. Branching from the current tip is okay.

Updates #46229

P.S. I haven't found any documentation on dev branch conventions and procedures, so I'm not sure whether it's appropriate for me to request this, and am just trying to replicate some previous dev branch request issues. Feel free to point out any issues!

P.P.S. Because the LoongArch ABIs might take a very long time to settle (perhaps due to circumstances I don't have position to comment on), a decision to postpone review work, and explicitly telling us to first polish things up out-of-tree, is okay from my viewpoint. I'm requesting a dev branch because I think it's important to collaborate as closely as possible for bringing up a new port, and for ensuring code quality by making individual changes step-by-step and have each one reviewed.

@ALTree
Copy link
Member

ALTree commented Aug 6, 2021

cc @golang/release

@ALTree ALTree added the NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. label Aug 6, 2021
@mengzhuo
Copy link
Contributor

hi, any updates? @golang/release
I can create a new branch in the gerrit if this proposal approved.

@ALTree
Copy link
Member

ALTree commented Aug 9, 2022

Closing as outdated, as the port was completed out-of-tree and then merged.

@ALTree ALTree closed this as completed Aug 9, 2022
@golang golang locked and limited conversation to collaborators Aug 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made.
Projects
None yet
Development

No branches or pull requests

4 participants