From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) by sourceware.org (Postfix) with ESMTPS id E04CF3858294 for ; Wed, 29 Nov 2023 13:41:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E04CF3858294 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=beagleboard.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org E04CF3858294 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2607:f8b0:4864:20::32c ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701265266; cv=none; b=wj4QCcRp+IKCZNuEBpZ9IssIgB0hi5F2kFPYWAOjX1O3M4w6C2xE4GHK4IJQm0aBwkTgENwK9nfrxVczCxhEKwQyMU7+C5nhkMerteG1OFc9aoEr735QdP/5w9xl/QoiMzqVUFwK9GflgdAnsBro68QIGRkL4vAZKpNU5JRJjdQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701265266; c=relaxed/simple; bh=igZnm77Jk7hcBjhbvF9Rb2FnXQoj1Ra5kGy8qkHo6fA=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=qokQGIVLNc09Y3PJ/bTGfsPxNp7AuttjPdH8nievIY9xJWqKHOaaUMj0sDQ4nhuqF8vAOkODU9hcy187S3jXRHLsqGE7W+ZHBrL8dXLf6VHDrXdYTQpIrwnOhsrNvJDv6CMP31MZ19XaY3lDkmek5VLW1Fci49ytpUkA1jQpAfI= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-ot1-x32c.google.com with SMTP id 46e09a7af769-6d84ddd642fso400621a34.0 for ; Wed, 29 Nov 2023 05:41:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail-com.20230601.gappssmtp.com; s=20230601; t=1701265262; x=1701870062; darn=gcc.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tO3AZXiuhhPFagSaKJQuiGZQtkGKQaRHjfjz/9KvRPw=; b=JAAju1618OsFx54bztiHaMg8/Yl1/hqymGQ9e6WZTESWkfM//WeWhO2bn1FxsvgWiT Bkt72gnMRzreXiNhKwYr8QpzUIjPs/BnqV1Ti68WiSqqMM2p+9U6N9jYvmBK5xeCzrCL SjPdlQAs7tEnREYad+cIGC2849hpO+yL5dE1G9JbZBqD0OVibRWC+dS4YsPidk6CGMIl h7/rnyI4LqjxJ9Afm9Iul74EHrbN4HLEDZyUNwl5wruNNky+xuc8Rsqg1qMGubIixo3J NYtv8AlSr++uP0WWnC709UHhWy4Sh6+XPliqZITWhjmTr12r8qg8qogPyujZV0gZSKFq n9uQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701265262; x=1701870062; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tO3AZXiuhhPFagSaKJQuiGZQtkGKQaRHjfjz/9KvRPw=; b=e9cgm/m/dEVd+Vecro+cDnqUaCzifEdO8c4ttW2DwI25t8lppmwT8YcPAONc95VgT3 9l1c23qz7WBggY2NobRhQmfinPrrojBhiqAfr4dyKBSGbBrk9XQwGQuOdG0xkWR/vW8b FhBWgeCnpAa2cqqcp3WVUnyejujrm2Gg6uwFLnHechYa32C3CbRR1Wz0UsviJYpUmThU MldmMllAkMbWX0vRw3rTgJmxpcSjm9MSSpihA+6Iq1NLgo0eXoQ/hDHnmdapS4KHtwUD ntxo9arL+5rtOkQum9WWcyBsl3+qt5qoTaDFTeL8u4xhicW+wCrCbFxmvGOfVdv9PzeD 1t0A== X-Gm-Message-State: AOJu0YyYrCgg5zAV33EbdgBbepSueJEedf7Eloc8V14imE9fEgfb/kiY yJqETDQPE9UuX6SYrBJrlCjjnEYJgYj2wIEo6Sw= X-Google-Smtp-Source: AGHT+IF4vx0+gdb2jgwCCBE07pXz6s8BWe0msa6AC2ZB3zcG/meCKMazGWd3JlrrCFjB46XRogUePFmu9zwch/AnVCY= X-Received: by 2002:a05:6871:7588:b0:1fa:25e2:efa8 with SMTP id nz8-20020a056871758800b001fa25e2efa8mr15762868oac.15.1701265261918; Wed, 29 Nov 2023 05:41:01 -0800 (PST) MIME-Version: 1.0 References: <29005844-ed33-4134-a7bd-824b1db7cee3@gmail.com> In-Reply-To: <29005844-ed33-4134-a7bd-824b1db7cee3@gmail.com> From: Jason Kridner Date: Wed, 29 Nov 2023 08:40:50 -0500 Message-ID: Subject: Re: T-Head Vector for GCC-14? (was Re: RISC-V: Support XTheadVector extensions) To: Jeff Law Cc: Philipp Tomsich , Palmer Dabbelt , christoph.muellner@vrull.eu, juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org, Kito Cheng , kito.cheng@sifive.com, cooper.joshua@linux.alibaba.com, Robin Dapp , cooper.qu@linux.alibaba.com, jinma@linux.alibaba.com, nelson@rivosinc.com Content-Type: multipart/alternative; boundary="0000000000009afe7b060b4aaf0b" X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --0000000000009afe7b060b4aaf0b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Nov 28, 2023 at 5:21=E2=80=AFPM Jeff Law wr= ote: > > On 11/28/23 12:56, Philipp Tomsich wrote: > > >> That's obviously a risky thing to do given it was sent right at the end > >> of the window, but it meets the rules. > >> > >> Folks in the call seemed generally amenable to at least trying for 14, > >> so unless anyone's opposed on the lists it seems like the way to go. > >> IIRC we ended up with the following TODO list: > >> > >> * Make sure this doesn't regress on the targets we already support. > >> From the sounds of things there's been test suite runs that look fine, > >> so hopefully that's all manageable. Christoph said he'd send > >> something out, we've had a bunch of test skew so there might be a bit > >> lurking but it should be generally manageable. > >> * We agree on some sort of support lifecycle. There seemed to be > >> basically two proposals: merge for 14 with the aim of quickly > >> deperecating it (maybe even for 15), or merge for 14 with the aim of > >> keeping it until it ends up un-tested (ie, requiring test results are > >> published for every release). > > > > We expect real-world users, including the BeagleV-AHEAD community, to > > need support for the foreseeable future. > > Keeping it until it ends up untested (and test cases are reasonably > > clean) sounds like a good threshold to ensure the integrity of the > > codebase while giving this a clear path to stay in for its useful > > life. > I can live with it being in the tree as long as it's maintained > (measured by ongoing testing with reasonable results). > > I'd proposed that it could end up deprecated quickly, but that was based > on the assumption that once V1.0 compliant hardware was widely available > that we'd see less and less interest in the thead extensions. > At BeagleBoard.org, we focus on long-term support and availability. Long-term support is a key for us engaging with education, both institutional and continuing, and industrial automation. Getting this into mainline such that we can develop solutions that integrate with mainline Linux distributions is key for us to enable broader RISC-V adoption. If it is deprecated at some point, that won't be terrible as long as we are able to get to a good snapshot where integration with the rest of the open source developer community has reasonably happened. The good news is it *will* get tested. We have confidence in that side of things. We have a great community that will engage the compiler and identify regressions. My expectation is that the Alibaba folks really know the C910 CPU core and will help us get things right. I'll be here to help escalate issues to them if they become unresponsive to the list. Others involved in the BeagleBoard.org project will help make sure I know when I need to escalate such issues. Let me know if there's anything I can do to encourage this being merged and worrying about deprecation later. -- https://beagleboard.org/about/jkridner - a 501c3 non-profit educating around open hardware computing --0000000000009afe7b060b4aaf0b--