From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) by sourceware.org (Postfix) with ESMTPS id 5119E3858D38 for ; Sat, 18 Nov 2023 10:33:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 5119E3858D38 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 5119E3858D38 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2607:f8b0:4864:20::229 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1700303583; cv=none; b=wixP4ry3G1kbII00PP4DbPRt8vsUpJn6auOYlb5Thw+gB0j8+ZW1wyC7b+RsF0Tc6BFJ/sjnej8N+zvCiUnvA35p6Nd5y1+LuA3bd2YRa3FvHi0IFzZ5XTh5U8dDy1ushKZZhIjhsQehJAZ6nLnOWqveJJT1tOJLwOLBoeyeNJ0= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1700303583; c=relaxed/simple; bh=DipiVhLHd/KwC0mvz8X8SRSzQpDhHSkq717tFAH8PPk=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=d0hvWPXINBW6axdHjalwopnZcuqtK3gJWurxqHeACBMsbcmR2MlG/c5HZVNu0O+M2cZKXJNcB7/tJL5YXvuDvE4JTuBDV8iJcWXqHs/Nxzqc0cN6pwy4IW70t7QCZDYhSX+ZJIo1u7clfepvOWhV7/k0WlOwpb0xCDZKsvCr4vo= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-oi1-x229.google.com with SMTP id 5614622812f47-3b40d5ea323so1897629b6e.0 for ; Sat, 18 Nov 2023 02:33:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700303581; x=1700908381; 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=DipiVhLHd/KwC0mvz8X8SRSzQpDhHSkq717tFAH8PPk=; b=TOuqtKghFBalRI+PDjCNRXwXINk5Kp286aNtqID064UrvjxYnjBvkOj4aKJZOz+BkA odhRhNxW/WhkZTPfHVn1+t6lj0o4w7IFzNYCYxHhqLjBbmzgP/KarZj0Jcf9lMxB9m2q oHURGUUflBnmYtophOFFSCk5491mfsuZoZ8WycCatPe5YNk5VE2ZqS6ib8qXZLF7kZZb sn1eog/x8QJAAWdgNCQIs6BR8A1aKExw1K3duRYLL9KS9uCPzwW64TpXP+51zTxAeE6E QBt8fjh7nCY0KMgn7NncTjtpmBDhA82+RRL7lybv4uJPEw3thLoEFkeaL4XOiTcvDGLj DlFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700303581; x=1700908381; 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=DipiVhLHd/KwC0mvz8X8SRSzQpDhHSkq717tFAH8PPk=; b=F7D/7MYYV4ck6mi5k/cvYcMGAOv9RIZpsFiXaV9v5XLNecOIfBtoCms3lS0VLPZXrs SXWaVEQVCb3vwbndZwYKIRTcSzXsPZxC7/v9vx9NIsgqlK+Qh4NHrrYFd6QuwTbmrP16 VdC4v1RhVSTQvyA2I0Gh6OcZXeIvYtmkzrRh/XqANOoH1nJ152xaqAgs8aZmlbkEqyyz GVIJ21QUD+0BzFyuI8e1k2XyTFJASL5G0m2OFUXSE8HeVlGtfjeeqBbB8kZ3h8/Pre4J aGSeA+cWyc6wHwE41pZhWHM7B+QY9SEz373ElB6Rg8Odwr+BHMs0xxWZGx3rY3cQY//a g45w== X-Gm-Message-State: AOJu0YxdS50s4bCDJrJaWUehB5LpvMxG78vUsXiEIzvHMjQBDLw9m0XE gmmKGW7sKglzeNyl4LuAwDdAH9+Z9FLXAu7eadw= X-Google-Smtp-Source: AGHT+IGgTA0FWZNPGmZ2PKClYkEsPDqX63CPdCZ+NRT6MvhrvbS+AmvzStRQIrgIjNtTyD24Dere5mJdAbQWAtJbmYM= X-Received: by 2002:a05:6870:788c:b0:1e9:9180:6f60 with SMTP id hc12-20020a056870788c00b001e991806f60mr2482306oab.23.1700303581448; Sat, 18 Nov 2023 02:33:01 -0800 (PST) MIME-Version: 1.0 References: <086123810F5FEA3C+202311171939484236058@rivai.ai> <534975f1-c062-49d5-a9e8-794260a0aba3@gmail.com> In-Reply-To: From: Kito Cheng Date: Sat, 18 Nov 2023 18:32:47 +0800 Message-ID: Subject: Re: RISC-V: Support XTheadVector extensions To: Philipp Tomsich Cc: Jeff Law , "juzhe.zhong@rivai.ai" , gcc-patches , "kito.cheng" , "cooper.joshua" , Robin Dapp , jkridner@beagleboard.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: I guess it would be worth to state my thought publicly: I *support* adding the T-head vector (a.k.a. vector 0.7) to upstream GCC since T-Head vector already ships a large enough number of boards, also it's not really T-head's problem as Palmer described in another mail. My biggest concern before is T-head folks didn't involved into community work too much, so accept that definitely will increasing work for maintainers, however I saw T-head folks is trying to contribute stuffs to upstream now, so may not a concern now, also I believe accept this patch will encourage they work more on upstream together, which is benefit to each other. Back to the one of the biggest issues for the patch set: GCC 14 or GCC 15. My general thought is it may be OK if it's less invasive enough, then should be OK for GCC 14, but I don't have a strong opinion, since as you know I am not the main developer of the vector part, so I will let Ju-Zhe make the final decision, because he is the one who contributes most things to RISC-V vector gcc support.