From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) by sourceware.org (Postfix) with ESMTPS id 331E73858C50 for ; Thu, 31 Mar 2022 06:21:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 331E73858C50 Received: by mail-wr1-x42a.google.com with SMTP id c7so5601954wrd.0 for ; Wed, 30 Mar 2022 23:21:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=thldl6NDXImj44PK6/6Dq9cpHXGWU5lrktP2GmL44SM=; b=jj4kBPNmGMtK+erP2IAKCfJuJQjnpdMB3Sh9jNCASYn6WGlq4jA5Aa/nzZCHKLJXrk yV8T//UGbpfbbbyOPN+UDxrXgVZlz2G4I01oqKk/MY5Cr51wKGn/DiDnTOM2bF3nWlcQ Oq8QlDuSFPktCsHlFha/OSxM4Nv2ayAXpNSwsQsj/qQkNPhtSccgbNUSEaFmFj6N7EZ/ TOtZLrNXAl4CgBpGO5pZ2Om00Z6mSQPs9hxcK20zhNQgoaM7jech3YZ/tm/QkBmEi1mS OUZ1XjENrcc7P10UgH4NP+JZMDY42iZ12ndrLBd3B691FPtxVAkNZNUr2tdgAYGPJG8t VDiQ== X-Gm-Message-State: AOAM531E6y7kEL4Dk8xgcrNdpbRcpgHwUTVlirEZtdt2JVA4aeTTiWid wDr6MHu9dnFWMgT1BveugKfcag== X-Google-Smtp-Source: ABdhPJzsQw4sPHrFU9zWY+W/QWUoE0Pj1ZOAXDgIhaoOD1bRFno4I25UVad+ewymu6N/tej0mfmjgA== X-Received: by 2002:a5d:4101:0:b0:205:86cb:dd1b with SMTP id l1-20020a5d4101000000b0020586cbdd1bmr2739321wrp.480.1648707712779; Wed, 30 Mar 2022 23:21:52 -0700 (PDT) Received: from google.com (110.121.148.146.bc.googleusercontent.com. [146.148.121.110]) by smtp.gmail.com with ESMTPSA id v5-20020adfe4c5000000b001edc1e5053esm18437737wrm.82.2022.03.30.23.21.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Mar 2022 23:21:51 -0700 (PDT) Date: Thu, 31 Mar 2022 08:21:48 +0200 From: "Steinar H. Gunderson" To: Jan Beulich Cc: Alan Modra , sesse@chromium.org, binutils@sourceware.org, Nick Clifton Subject: Re: [PATCH] Add a trie to map quickly from address range to compilation unit. Message-ID: References: <20220321094030.1256430-1-sesse@google.com> <63191455-2374-5db9-f55e-ddf794c7d88e@redhat.com> <49afcaee-63a8-2d18-64d1-0fc0abfe4669@suse.com> <6c45bf8e-00e5-f7c6-025b-e4b9c3832da3@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6c45bf8e-00e5-f7c6-025b-e4b9c3832da3@suse.com> X-Spam-Status: No, score=-18.8 required=5.0 tests=BAYES_00, DKIMWL_WL_MED, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE, USER_IN_DEF_DKIM_WL, USER_IN_DEF_SPF_WL 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: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2022 06:21:55 -0000 On Tue, Mar 29, 2022 at 08:07:07AM +0200, Jan Beulich wrote: > Yeah, makes sense to me. I guess if bad input was to be worked around > again, a testcase covering the specific situation would want adding, so > it won't be lost what specifically is to be worked around. I'm fine with just removing the range handling logic if that's what you decide. :-) Let me know when/if a patch goes in, and I'll send a v3 that is adjusted. /* Steinar */