From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) by sourceware.org (Postfix) with ESMTPS id D9CB33858C50 for ; Wed, 4 Jan 2023 01:03:34 +0000 (GMT) Received: from cmgw15.mail.unifiedlayer.com (unknown [10.0.90.130]) by progateway4.mail.pro1.eigbox.com (Postfix) with ESMTP id 6E43010046B1D for ; Wed, 4 Jan 2023 01:03:21 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id CsBdpBK8KRAcHCsBdpPU1v; Wed, 04 Jan 2023 01:03:21 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=F72SyotN c=1 sm=1 tr=0 ts=63b4d059 a=ApxJNpeYhEAb1aAlGBBbmA==:117 a=ApxJNpeYhEAb1aAlGBBbmA==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=RvmDmJFTN0MA:10:nop_rcvd_month_year a=Qbun_eYptAEA:10:endurance_base64_authed_username_1 a=dzWzf_mpAAAA:8 a=CCpqsmhAAAAA:8 a=YD9mUYWVNByF25WWQEIA:9 a=LmWSLzVEShUA:10:demote_hacked_domain_1 a=b4DR9a7p2ZdsqdHBznES:22 a=ul9cdbp4aOFLsgKbc677:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References :Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=ByatEJvFOQFkikHyqa8Z6uS6O62iAH3dbyfLLHIoIMk=; b=QuCWeBiznypJr6DW4sHdVukomy /TC5O/t1qXfIwc4mUHZn1ab92rjS2rDbuxBZlplI20c7CI/BOvFgA1/NeXzCx9eVGRzdJ8WLhDBYQ QeJnRZVJMLkZm6tQOgaoh/10b; Received: from [161.98.8.3] (port=34620 helo=prentzel) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1pCsBc-003JFc-LA; Tue, 03 Jan 2023 18:03:20 -0700 From: Tom Tromey To: Simon Marchi Cc: Christian Biesinger , Eli Zaretskii , tom@tromey.com, gdb-patches@sourceware.org, luis.machado@arm.com Subject: Re: Two observations using GDB 13 snapshot References: <83h6xugc5v.fsf@gnu.org> <835ye7e9jw.fsf@gnu.org> <87h6xrks77.fsf@tromey.com> <83mt7idacj.fsf@gnu.org> <87fsd4elb2.fsf@tromey.com> <83o7rs4qmg.fsf@gnu.org> <87cz84dasj.fsf@tromey.com> <835ydw20bw.fsf@gnu.org> <87wn6bbi5m.fsf@tromey.com> <83sfgz8m9i.fsf@gnu.org> <87o7rnb0ya.fsf@tromey.com> <83a6368chf.fsf@gnu.org> <87k02aaxc8.fsf@tromey.com> <83wn6a6n21.fsf@gnu.org> <587b899f-0f93-530a-7313-d4e1f9e501b9@simark.ca> <835ydt6jzw.fsf@gnu.org> <83wn63z81w.fsf@gnu.org> <46d7fd4b-d5f0-0007-3e88-20345e0e0584@simark.ca> X-Attribution: Tom Date: Tue, 03 Jan 2023 18:03:17 -0700 In-Reply-To: <46d7fd4b-d5f0-0007-3e88-20345e0e0584@simark.ca> (Simon Marchi's message of "Tue, 3 Jan 2023 16:34:53 -0500") Message-ID: <87h6x79kmi.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 161.98.8.3 X-Source-L: No X-Exim-ID: 1pCsBc-003JFc-LA X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: (prentzel) [161.98.8.3]:34620 X-Source-Auth: tom+tromey.com X-Email-Count: 4 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3021.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,JMQ_SPF_NEUTRAL,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: >>>>> "Simon" == Simon Marchi writes: Simon> It would be interesting to change that strcasecmp call to strcmp, just Simon> to see if it makes an impact on the performance. Whether or not that Simon> would be correct is another thing, but it would help see if that Simon> strcasecmp / tolower call is really at fault here. My series to fix the template lookup problem avoids strcasecmp in favor of a hand-written alternative. So, I guess it's possible it would fix this bug as well. The patch that does this in particular is: https://sourceware.org/pipermail/gdb-patches/2022-December/194799.html I wonder if it's possible to do the sort case-sensitively. I thought this was for Fortran and/or Ada, but I'm not really sure. For instance it could also possibly be solved by case-folding the lookup name. At least, that's true for Ada, because GNAT already case-folds the DWARF names. Not sure about Fortran compilers. Anyway, also not something I'd want to experiment with just before the release. Tom