From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by sourceware.org (Postfix) with ESMTPS id 5AF1D3856948 for ; Fri, 5 May 2023 15:38:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 5AF1D3856948 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=suse.cz Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 886D3201C8; Fri, 5 May 2023 15:38:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1683301104; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=EonxXyC8plLan3lWV5dflWuv9c5qeYSYPgsNHhJXDZQ=; b=LN+G36EX4I4zpDhdqK/T/X5wo6iBwGgogV/2yL1ehFaKFeWRxVOQlQBbBXkbr0e2faHSAy QRaiX/rH3u5izdvZpCrVpCxugfRrLON4azPCzXGMTVkrsmuSOt2IWK94MwWdyt1EnQnAAt Tc7i827ClDP9jeJashYAO1rmstS2hcw= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1683301104; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=EonxXyC8plLan3lWV5dflWuv9c5qeYSYPgsNHhJXDZQ=; b=D2t+XiO35ln3BN74lUvqfOJAj9uH8PXTYO4Grrqa1EfYn/r9Mfpi5G0nAKW/srHKvKAT8c 1tciGmLnPmsTDlBQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 7AE61139F8; Fri, 5 May 2023 15:38:24 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id ap57HfAiVWQeFQAAMHmgww (envelope-from ); Fri, 05 May 2023 15:38:24 +0000 From: Martin Jambor To: Aldy Hernandez , GCC Mailing List Cc: Andrew MacLeod , Richard Biener Subject: Re: Upcoming removal of legacy ranges and conversion to wide_ints. In-Reply-To: References: User-Agent: Notmuch/0.37 (https://notmuchmail.org) Emacs/28.2 (x86_64-suse-linux-gnu) Date: Fri, 05 May 2023 17:38:23 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-5.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,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: Hi, On Tue, Apr 25 2023, Aldy Hernandez via Gcc wrote: > After GCC 13 is released we will remove legacy range support from the > compiler, and convert irange's to wide_ints. I want to give everyone > a heads up, to help understand what's involved and what the end result is. > [...] > > 1. Converting users of the old API to the new irange API. > [...] > > The IPA passes also use the old API, but I have plans (and patches) > for revamping all of the IPA ranges. Details below. Thanks a lot for taking care of this. [..] > IPA has been rolling their own ranges forever. They use a combination > of the legacy API along with handcrafted pairs of wide_ints (ipa_vr). > The passes must be divorced of its legacy dependency, and cleaned up a > bit. IPA is also very tied to integers and pointers, and I see no > reason why we can't keep track of float arguments, etc. Agreed. > > I am sitting on a lot of additional patches to do 90% of the > conversion, but need to consult with the IPA experts on various issues > before proceeding (for instance, the lifetime of various structures). > Among these patches are generic vrange LTO streaming functions and > vrange hashing. I think it's time we make vrange a first class > citizen for LTO/hashing and a few other things folks were doing in an > ad-hoc manner. This should alleviate the maintenance burden on the > IPA maintainers going forward. Note, that the IPA work is a > follow-up, and only after careful consultation with the relevant > maintainers. I need to get up to speed when it comes to the new representation and new API but I'll be happy to help. Martin