From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) by sourceware.org (Postfix) with ESMTPS id B141C385803F for ; Fri, 16 Apr 2021 02:33:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B141C385803F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=sifive.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=nelson.chu@sifive.com Received: by mail-io1-xd34.google.com with SMTP id v3so4810128ion.12 for ; Thu, 15 Apr 2021 19:33:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dsS9KpGeVALfWpk8NYPY318HgNbmsPE2XszXnW0zFaQ=; b=AA0cUBIYeUrIYw4yqzwnsE39OwkknZYkEyHw+/IgTffC4eX2LpX+L+3/4gr86J5nN6 G4L2UjmmheVEPR+bT9R03Fp6YjhsJxGt3m6rQm+tS+vcxKkA2aCm6yMyu6XX31Jj9xnu NxW1A0D00ZjA5is0d/En56gWVZDAgNNa30vixIIm3ARJj6TN3WYxi8tUggMKzq8NU5St QacL8Kp4mPIsFks0dz+myVPzPsYv2/+vLP0OTYMhmV2SrJiKYQCdU1naFydyi73VghX1 dLH1F98uGYxAceUHaAeBvnQ3eiCzQUDkBGPbbB2ek/smD5blVCkEBbPwTAqHmk6I1IR7 KTkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dsS9KpGeVALfWpk8NYPY318HgNbmsPE2XszXnW0zFaQ=; b=tCSGzsdAAuigzrVgjcXeAbQMTmEbSg6N75+TvQdlsZooqRMM/077jvGS4nfSbseQrm 0ZwE4/NISsZj3JjsYml8oqDs+iOWcjzMJyrYBBn2n99WxbTxWyEGCTvERiQqGJblm998 Ha9KO6SwIqdfWLwCG6T+DxLTuvLH2VIpOPSGIPh1oictMBtnCcTxWgKt76nX6smusdEX ARFLVWZtMM8Vobl8G7zHD3evjnyr74kjrUrZerSDsx7UnCGWXUHi4dqC65Xm3HEQ9Dxm IkBNB+E807XorN3wP5QnKunwq6SNGFPLKTw3uMZpRJwKy6ZXablAHf8c7/fMXpLqgNsG SwMA== X-Gm-Message-State: AOAM530NG78iwOVmjNuoYArYsseMTE5RZgYMml+diBLUM/BM0+LxEZe0 Nm3XZZ06fa4aHKk4uQQiFntJhK82t0bsPw5O3la8og== X-Google-Smtp-Source: ABdhPJy6l+6eEJQiK0OZwGJu6nc8KRowiwImk4+noRvCoc1Iv9MGXFpGGnqTtZZJ+mbPNSwRmB5aAZrJtddyWn+joGU= X-Received: by 2002:a05:6602:24d4:: with SMTP id h20mr1777285ioe.4.1618540380017; Thu, 15 Apr 2021 19:33:00 -0700 (PDT) MIME-Version: 1.0 References: <1617097017-16776-1-git-send-email-nelson.chu@sifive.com> In-Reply-To: From: Nelson Chu Date: Fri, 16 Apr 2021 10:32:48 +0800 Message-ID: Subject: Re: [Integration 0/6] RISC-V: The prototype of the integration and working branches for binutils. To: Jim Wilson Cc: Binutils , Alan Modra , Nick Clifton , Kito Cheng , Andrew Waterman , Palmer Dabbelt , Simon Cook , Jeremy Bennett Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2021 02:33:04 -0000 On Wed, Mar 31, 2021 at 7:16 AM Jim Wilson wrote: > > On Tue, Mar 30, 2021 at 2:37 AM Nelson Chu wrote: >> >> RISC-V GNU binutils will have another two FSF develop branches to let >> developers can contribute their works, but these works are not ratified >> yet, so they aren't allowed to merge into mainline. The two branches are >> integration branch and working branch. The series of patches are the >> prototypes for these two develop branches, and they won't be applied to >> the mainline. Please see the details in the comments of the patches, >> and feels free to share any thought and suggestion, if you are interested. > > > The series looks OK to me. I made some minor comments, other than the Zfh fcvt.q.h and fcvt.h.q which I think are broken and need to be fixed. Oh forgot to mention that I have fixed the following issues, and then sent the v2 series of the patches yesterday. * Removed the vendor stuff since it is still discussing, so only keep the draft v and zfh at this stage. * Fixed the header issue (data and author) for the new added headers. * Fixed the wrong encoding of fcvt.q.h and fcvt.h.q. * Added f as the implicit extension of zfh, and changed INSN_CLASS_F_AND_ZFH to INSN_CLASS_ZFH. I see that ARM had created their branches in the user folders, remotes/upstream/users/ARM/embedded-binutils-2_26-branch remotes/upstream/users/ARM/embedded-gdb-7.10-branch remotes/upstream/users/ARM/morello-binutils-gdb-master remotes/upstream/users/ARM/sve so RISC-V probably can create our integration and working branch to /users/RISCV/riscv-binutils-integration-branch /users/RISCV/riscv-binutils-working-branch These branches are based on the mainline, and will merge the features from mainline regularity. I cannot find any spec or discussion that mention the branch names, so the above names can be changed before we created them. However, I don't know if we need to have the stable released branch with specific versions of the draft/vendor features. For example, we are working on the riscv-binutils-integration-branch which is based on the manline. Once the new stable released branch is created, like 2.37, then we should create the riscv-binutils-integration-2.37-branch, and port the features from riscv-binutils-integration-branch to there. Therefore, we may have the following branches in the future, /users/RISCV/riscv-binutils-integration-branch, with newest zext v0.9 /users/RISCV/riscv-binutils-integration-2.38-branch, with zext v0.8 /users/RISCV/riscv-binutils-integration-2.37-branch, with zext v0.5 ... Or we don't need to do this, just keep the riscv-binutils-integration-branch with the newest versions of drafts, and based on the mainline. This is not very urgent, so we still have time to discuss it. Anyway, if the name of the branch is fine to you, I will create the /users/RISCV/riscv-binutils-integration-branch first recently. Please feel free to share your thoughts and suggestions. It would be great if you can send the mail to me or reply to this mail directly. Thanks Nelson