From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) by sourceware.org (Postfix) with ESMTPS id ADCCE3858D1E for ; Tue, 25 Apr 2023 06:00:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org ADCCE3858D1E 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-pf1-x435.google.com with SMTP id d2e1a72fcca58-63b73203e0aso32970839b3a.1 for ; Mon, 24 Apr 2023 23:00:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682402421; x=1684994421; 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=wsyxRW6+0PbFB7N8Li+hbCKYkQWHSgsBPuAilMgAqpc=; b=Xw4Q/EPVFYaHnqX6Sniq7+5C04Q9iDMiptf6Mhggao3eA8mNpFpcldr+VYq6CdnF/C wCA2qz48Fqm0qLWQR05BWcQClU1eSTgYCXazCv0dg5IDR7c6+pcx7pw1cVimbdZ37SRI fhMnjgx6KZe2Jihq23oNMsmvUpk5TqRt6+gXRULm8skucnnn/edYz8s0CXS8IT/mBeVe vUCXIQsZ0Em35IRklRHPHtH20vpfYiSdSpDb78OKDXYxHW+bZDKnBO6R7RA+JL1Xkk9x 1OXO3VnFh1vC0OTfJ0q23fC76mnJtBqQva/Z14bS2L//066l6ssojhEJpjOD8lS/ukDi YorQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682402421; x=1684994421; 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=wsyxRW6+0PbFB7N8Li+hbCKYkQWHSgsBPuAilMgAqpc=; b=O6ChHaWLxjnSnx8a7jQsGZZbGGgg5EcJnT1Ve7Wr/KouAfIvylNFOKrJZm0+DZlFWd ax/Snfahsd3eUeUn3BX84/nc6DG1+nIvV1f1ZINXF0j4uTijwJMmV7XyZ4UdAVxTQWSE a5DS0JjYHtRZcaN9c9maYqZ1GRO27+Hwlhg2NSEXU2l5kKrhZn9daQ3uI1PnAVKxthoQ tFPr3enzhVYcU6FpJActuNMmvPhesBiQCJO/NOmdBCOUBe2Hpbcm0vZuKaUpwN6IaGZ3 sjOXjIRtNx4HNt+7+G4t3kX+9g73f3th2fFBDv2MfdDckUr5NNu7n2wOsczm9ly90QLA Fkhw== X-Gm-Message-State: AAQBX9f1Bk0zNOFRZLAc3yQgIw2tMCTBYx1fUXkdzTGlBy3ZyBC+gWEE S4kvlF0+FSadlEbZIPYlr6o= X-Google-Smtp-Source: AKy350YYlQMqsmbhXnll2jb3pxN2gVjz3LXWVBxtTSdeYRCrXIGi84j7J1X7H9j1fDr1muRAler1sw== X-Received: by 2002:a05:6a00:2e04:b0:63d:3981:3118 with SMTP id fc4-20020a056a002e0400b0063d39813118mr16382180pfb.15.1682402421491; Mon, 24 Apr 2023 23:00:21 -0700 (PDT) Received: from ?IPV6:2601:681:8600:13d0::99f? ([2601:681:8600:13d0::99f]) by smtp.gmail.com with ESMTPSA id k24-20020a6568d8000000b00520b677c645sm7362256pgt.41.2023.04.24.23.00.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 24 Apr 2023 23:00:20 -0700 (PDT) Message-ID: <79710efe-0dcc-0412-95c5-13dd53ccefb0@gmail.com> Date: Tue, 25 Apr 2023 00:00:19 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: [PATCH] RISC-V: Add RVV auto-vectorization compile option Content-Language: en-US To: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org Cc: kito.cheng@gmail.com, palmer@dabbelt.com References: <20230407012129.63142-1-juzhe.zhong@rivai.ai> From: Jeff Law In-Reply-To: <20230407012129.63142-1-juzhe.zhong@rivai.ai> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.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,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: On 4/6/23 19:21, juzhe.zhong@rivai.ai wrote: > From: Juzhe-Zhong > > The next patch to enable basic RVV auto-vectorization of > VLA auto-vectorization (RVV_SCALABLE) and fixed-length VLS auto-vectorization (RVV_FIXED_VLMAX). > > We will support RVV_FIXED_VLMIN in the future. > > gcc/ChangeLog: > > * config/riscv/riscv-opts.h (enum riscv_autovec_preference_enum): Add RVV auto-vectorization compile option. > (enum riscv_autovec_lmul_enum): Ditto. > * config/riscv/riscv.opt: Ditto. No real objection here. Just a question. What's the rationale behind exposing lmul settings to the user? I'd think that should largely be compiler managed. But maybe I'm missing something. jeff