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.129.124]) by sourceware.org (Postfix) with ESMTPS id 1E9CC3857C72 for ; Tue, 30 Aug 2022 10:58:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1E9CC3857C72 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1661857121; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=JedNHLychVJHMEe1/iUmzUjTwbJiUSvl//8SqLk8NxU=; b=BhCzx8PJqRd3RjcCyf4B446xBC3/Pz90GWhuag4rTdE4H40aMeGgXyH+yo7uXXsgqrYML3 Mv5hneMYC44eNf741HVMMJsfieSTeomKOZCl4D0YU0sSgGzqjYPibHKlkVF021UyhsqeAD BkF9AlpEDhVwQPoZvw71mBGKvGIjF7k= Received: from mail-oa1-f71.google.com (mail-oa1-f71.google.com [209.85.160.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-99-j5QaFpp1Nl2rPjG4SlqwYQ-1; Tue, 30 Aug 2022 06:58:39 -0400 X-MC-Unique: j5QaFpp1Nl2rPjG4SlqwYQ-1 Received: by mail-oa1-f71.google.com with SMTP id 586e51a60fabf-1101032fd65so2776345fac.7 for ; Tue, 30 Aug 2022 03:58:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc; bh=JedNHLychVJHMEe1/iUmzUjTwbJiUSvl//8SqLk8NxU=; b=r3Fy4ZPLdcCzWXY4w+S4dmkbaidMauuiV98zDKq1TrRGr1YLniryNwTMYCb3+gv2ur z+recnWv40jYzeZEye2E6SLHxOLF76H8ojqGjXJbnDrXCokoPABgQo/Fa0cGmQESb/Vo IDVlE3oOhhlLeS4VVez6EoKjHYvTsafErECzy4g2EpsQd6w1mA2s0NgqQE2jPsCloxKp qJKa0fuHgaNU/8J84qdet+UrbxRtOflUxlfx/+wGMAntx2QRCbAKuNMlbogRQDZhP2lD zlumwoujbFAHohvelXGVJWNjIGepUkun+DPUdGM6m8CDr/pfVXuInkCxgf7H/XEJF5WK 1yhQ== X-Gm-Message-State: ACgBeo2mHt43LtMNAL1V4iioSNr8Y2EzqCIoGCaMCKOYjleNIcOFw6iw SwR3EQbUjekPJud5S5dX3aGPJcY5ra4/gCHSURvdyO4nchZIUXaDhgpM2tdwdZakrd/0V0YfYw3 5eJc8OhBA9aTSqFTTbowq3GrV1QRqIbCX7Q== X-Received: by 2002:a05:6830:6385:b0:61d:357:2077 with SMTP id ch5-20020a056830638500b0061d03572077mr8105803otb.359.1661857118731; Tue, 30 Aug 2022 03:58:38 -0700 (PDT) X-Google-Smtp-Source: AA6agR4hXUhf4kcKX1eYoLSKdIk5+O/oQ9ThneE61WdB3rnwcKrqOeduhSLP/kcM+VNeKJu5TQBRWlZAT1gHlMGksro= X-Received: by 2002:a05:6830:6385:b0:61d:357:2077 with SMTP id ch5-20020a056830638500b0061d03572077mr8105797otb.359.1661857118470; Tue, 30 Aug 2022 03:58:38 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ulrich Drepper Date: Tue, 30 Aug 2022 12:58:27 +0200 Message-ID: Subject: Re: [Patch] add more C++ name hints. v2 To: gcc-patches@gcc.gnu.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="00000000000036deee05e77343b0" X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_NONE,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: Message-ID: <20220830105827.FUJa_o5tcGPTG-1Ujw-KVLhIPixA5HF9Crvh2YTuVgk@z> --00000000000036deee05e77343b0 Content-Type: text/plain; charset="UTF-8" Ping! Anyone interested in this. I'm bootstrapping my trunk builds with this patch without problems. On Mon, Aug 22, 2022 at 9:09 PM Ulrich Drepper wrote: > This is the second version of the proposed patch to add more identifiers > to the known list to give hints about #include and version numbers. > > Marek looked through the first version and found it acceptable but > remarked that the list is getting long and the sequential search performed > by the current code might not be adequate. Especially because I offered to > add even more known names to the list. > > This second version replaces the current lookup implementation with a > gperf-generated hash function. Since gperf is already a dependency for > maintainers the use of the tool itself shouldn't be a problem. > > I followed the existing practice for the cfns.gperf file and its use so, > if the handling of that file works, so should the handling of the new file, > std-name-hint.gperf. > > Please let me know if this is acceptable. I built a compiler with this > code and tested the hinting. > > contrib/ChangeLog > * gcc_update (files_and_dependencies): Add gcc/cp/std-name-hint.h > depend on gcc/cp/std-name-hint.gperf. > > gcc/cp/ChangeLog > * Make-lang.in: Add rule to build std-name-hint.h. > * name-lookup.cc (struct std_name_hint): Remove definition. > Instead... > Include "std-name-hint.h". > (get_std_name_hint): Remove hints array and lookup code. Instead > call > std_name_hint_lookup::find. > * std-name-hint.gperf: New file. > * std-name-hint.h: New file. > --00000000000036deee05e77343b0--