From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 0615F3857361 for ; Mon, 9 May 2022 12:42:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0615F3857361 Received: from mail-qv1-f69.google.com (mail-qv1-f69.google.com [209.85.219.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-212-jETRthcBMQmb37bUeB9h7w-1; Mon, 09 May 2022 08:42:15 -0400 X-MC-Unique: jETRthcBMQmb37bUeB9h7w-1 Received: by mail-qv1-f69.google.com with SMTP id u19-20020ad449b3000000b004523cc11b95so11655958qvx.7 for ; Mon, 09 May 2022 05:42:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=+8Tx82aAMkdno8FPgtzvqdmRQwo8mdyI1/3be6cln1Y=; b=blgjhSpHewcobeQpjrrAMI/SXWLWwd3GtBXDychp/wSe1Bh/D09hHfYGJPEdOnMhTO BlAT9vkGnmsooGRMxALHl84KmGBdKS8LwzXnpbp202Zc0oQyYrh+mwguB+IrurkMeEqZ JiaT3F/L34LppLK75eKszxKYVb+1mnrDvkarWx4MxyKKvfGY4Jw9hyTyDeiggJboSWVL 7btbCbYmKkGDigM9bpTT93n5jF0FXBPR/hX12qIOFqeNgUXrCwWUeHfr7G/B2HcQbrgg WQEzcRtXWHgDUJEBiA7hvPwXAV3iTg6q3yNGVIIUWevL/9dsMfxqoXA24iPHgk7IOor5 hNXA== X-Gm-Message-State: AOAM530nAkdbwt6bH4ONBzP2yTYOf+LvN/59LdKCjpd5HdOUpDu5Oihu j62dKnkS2unDnoFq+rYG5mmW9JOJMbBzVJqjq/0PLliLh+Di4nYVVNML2zY48RbxwicFKGpF2kg +vKMAtVqgrQQREEbATQ== X-Received: by 2002:ad4:4386:0:b0:456:5223:7bd5 with SMTP id s6-20020ad44386000000b0045652237bd5mr13218416qvr.32.1652100134720; Mon, 09 May 2022 05:42:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyjr34tf+KYJaBucu1e2vvCkyzqlphGwGXh2jOeh6JrpPdI119TwvHRH+FW5o/8W1BZvZROwA== X-Received: by 2002:ad4:4386:0:b0:456:5223:7bd5 with SMTP id s6-20020ad44386000000b0045652237bd5mr13218398qvr.32.1652100134482; Mon, 09 May 2022 05:42:14 -0700 (PDT) Received: from ?IPV6:2607:fea8:a261:5e00::94b0? ([2607:fea8:a261:5e00::94b0]) by smtp.gmail.com with ESMTPSA id n23-20020ac86757000000b002f39b99f6b8sm7286883qtp.82.2022.05.09.05.42.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 09 May 2022 05:42:13 -0700 (PDT) Message-ID: Date: Mon, 9 May 2022 08:42:11 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH] Replace EVRP in DOM with ranger. To: Richard Biener , Aldy Hernandez Cc: Jeff Law , GCC patches References: <20220428163015.595263-1-aldyh@redhat.com> From: Andrew MacLeod In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-CA Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-6.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2022 12:42:18 -0000 On 5/2/22 02:30, Richard Biener wrote: > On Fri, Apr 29, 2022 at 6:22 PM Aldy Hernandez wrote: >> >> Andrew was mumbling something about a fast ranger mode for this >> release that should be on par with legacy evrp. IIRC it would be >> purely DOM based, won't visit back edges, and there's no caching. But >> he'll have to expand on it when he returns from vacation. I don't >> know the details. > I would guess the stmt analysis building blocks (whatever API part of > ranger that is) can be used to produce something like that. But in the > end it would be the old EVRP pass with the VRP stmt analysis it > re-used replaced with the appropriate ranger parts. > > But yes, I'd welcome that. I'd also like to revisit integration of some > of this with value-numbering which doesn't do a DOM walk but instead > a RPO walk. Yes, it will bear numerous similarities to the old EVRP mechanism approach.  It'd would use a similar "current value" vector, just using multi-ranges and wired into the range-ops/gori mechanism for calculating outgoing ranges on outgoing/incoming edges.  Its next on my list after I get a few outstanding things in. An RPO walk should be trivial to work with as well.  Is there generic infrastructure for RPO like there is for DOM walks, or is it more wired into VN?  Regardless, we should be able to set it up to work from anywhere. Andrew