From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) by sourceware.org (Postfix) with ESMTPS id D58373858D33 for ; Tue, 14 Mar 2023 17:48:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D58373858D33 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-pl1-x631.google.com with SMTP id ja10so7756890plb.5 for ; Tue, 14 Mar 2023 10:48:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678816107; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=xNPpcQNsHU+9zrrwIiq0AjCy/LNDkkofsP3sPBCCUXk=; b=LhSMXczKTeDATRG5hFZRdiPV6QkiOyYl8Bva5wNYfBAyv0sxXKQrxO/7Z/guyhNh40 M4U+CZ/thYb8+n8KkYNDasK747kjha4PqlUKR/zXtFoTrpHuQ25UjOW/ZD4NWTXcN80L c9ACuco0ti2XKoWVS/VhUY37Z/XK/TgV47oPdvu5hrgecAUTxfRs0Yu5Pjr48vJ8sxN9 kgNrQpMZ/frminivYOQDPTm+tBG5mVMlvxX3a807ps5avlPZj2iggiYxtVxQVahf51Mx WXGPUqQJ2q5T6hzWG5YWPVZ4m+KRbxxDAInGbPE9qXUoOwx3vvMD7M3Q1DRAF04t6Bw6 JDhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678816107; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=xNPpcQNsHU+9zrrwIiq0AjCy/LNDkkofsP3sPBCCUXk=; b=oBgxuo7XDQhEibbUQcSCEzUtZ1hwqPsY2fN1WEfsyR+GTPK11BUnLl8IcVv6mnWYLH gl0g3vKc/6I3MoR9+oIdrv7K5xmdgglawPQ7ZARXDH4SUwJGW5yzlKmhAiwhieLlb90B zqmY8EF6DxG0AhQE3HBo8VKV0H2ZDAYj87cOsglAkkSy1plStYaT15e5SywKMiTEgKpT kikhbmUrUxOajzQZeccwXn7cv7MQERekoKmhJJZJtHcE5hYaUUPXDPM2Ao65aMi+Mhck 8YUgtv+g8tzZ/fjJN7jpTmUfdi/f8aHfm6uyGLu43hOHni72jbYt+797yHc6mi527U7H 9fQg== X-Gm-Message-State: AO0yUKWuUdZzWLSALRvNZA27kw/kYP4NJrJOY374fincW2GcgGT7u/uN wmTKeCdPz5uP+TPjAvMi6x4= X-Google-Smtp-Source: AK7set+iuylN7wNDxkASf0m0JrZ0Cx78ojMrrPzv8ijYel8tr7Hiu/HymdpTQoDkr9DNo46QGnpCQg== X-Received: by 2002:a17:902:ecc1:b0:19e:23c1:4c2e with SMTP id a1-20020a170902ecc100b0019e23c14c2emr28210903plh.59.1678816106673; Tue, 14 Mar 2023 10:48:26 -0700 (PDT) Received: from ?IPV6:2601:681:8600:13d0::f0a? ([2601:681:8600:13d0::f0a]) by smtp.gmail.com with ESMTPSA id kj11-20020a17090306cb00b00198ac2769aesm2044119plb.135.2023.03.14.10.48.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 14 Mar 2023 10:48:26 -0700 (PDT) Message-ID: <01864d87-ce93-1e1b-926f-0a681a477ead@gmail.com> Date: Tue, 14 Mar 2023 11:48:24 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH] vect: Check that vector factor is a compile-time constant Content-Language: en-US To: Kito Cheng Cc: Michael Collison , juzhe.zhong@rivai.ai, gcc-patches , "kito.cheng" , "richard.sandiford" , "richard.guenther" References: <69622113-9b9f-f93d-b89d-0783b95bbfcb@gmail.com> <71276340-3acc-c700-d7b5-3f388442295b@rivosinc.com> From: Jeff Law In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP 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: On 2/23/23 21:04, Kito Cheng wrote: > Hi Jeff: > >> What I'd been planning to do internally at Ventana was to update our >> codebase to gcc-13 once it's released. Then I'd backport RVV autovec >> work from the gcc-14 dev tree into that Ventana branch. >> >> Instead, but along the same lines, we could have a public gcc-13 based >> branch which follows that same process and where Rivos, SiFive, Rivai, >> Ventana (and potentially others with an interest in this space) could >> collaborate. Essentially it'd be gcc-13 + RVV autovec support. We'd >> probably have to hash out a bit of policy with the shared branch, but >> I'd like to think we could make it work. > > +1, I like the idea, I could imagine we definitely will do the same > work more than four times by different companies if we don't have a > collaboration branch... So it looks like there's a general sense that a coordination branch off gcc-13 is reasonable. So I'd like to hammer out a few details. First, I recommend we cut a branch from gcc-13 soon after gcc-13 branches. That way we've got a place to land the vector work. Second, I recommend we rebase that branch periodically so that it follows gcc-13. That means downstream consumers may have non-ff pulls, but I think we want to follow gcc-13 fairly closely. I'm open to other approaches here. Third, I was thinking that once a patch related to risc-v vectorization goes to the trunk, any one of the principals should be able to cherry-pick that patch onto our branch. That implies we need to identify the principals. I'll suggest Kito, Juzhe, Michael and myself as the initial list. I'm certainly open to others joining. Other thoughts or suggestions? Jeff