From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) by sourceware.org (Postfix) with ESMTPS id B46403943404 for ; Mon, 21 Jun 2021 21:37:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B46403943404 Received: by mail-oi1-x22a.google.com with SMTP id x196so21474385oif.10 for ; Mon, 21 Jun 2021 14:37:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=UbKZX5thAX2a6un8h/jtezuyytf8GFu8K6u48lK+aAw=; b=Ch+6WHPwb+7UKekxEz+bUw++WgK0R1mgmF8/wG8LfAYX7YkjXoy7+h7AKEtY3mrbGI 7gBJu02I+0Jaugb55tKXqccscWKYVOXpNRbAsu1SHVCzgtmYit+3KagIPY1xBOBUYpyS H5rwMLlsCXaf4SoHPevXS1V63B+S6wORLITcU2V0LE/UmkwgySWR5c8OQdlbBRgdb7oU T4UlIUCwMUTpMT5wnuSdCUCO0SnGQzbLKkrXNLzXZYqTwi9Z+oyfu5/1SiNtbsQROlpi rwnF3dCvUreb6ryMe1HP4Tg+pwOCSTp/ePHQTMbXrUnzRw/+zcwQgyDgD6OS+GNFQmGg Dmow== X-Gm-Message-State: AOAM533fry7MUJ3CLcqpedBMxFqVnTmIOUxakmZibAUXP0Ah/BxnJ+sp mGVlmPbOb9TkjZuGdi8/CHs= X-Google-Smtp-Source: ABdhPJyEbeJm2fjNdxbshLFCJCpaWOJoIiTUbcwd4L8Z7zAzwa8x3MvlQ7jlpNxv7lcsgb1F95aq/Q== X-Received: by 2002:a05:6808:649:: with SMTP id z9mr367526oih.149.1624311442175; Mon, 21 Jun 2021 14:37:22 -0700 (PDT) Received: from [192.168.0.41] (97-118-105-195.hlrn.qwest.net. [97.118.105.195]) by smtp.gmail.com with ESMTPSA id w5sm1506906oiv.7.2021.06.21.14.37.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Jun 2021 14:37:21 -0700 (PDT) Subject: [PING][PATCH 6/13] v2 Use new per-location warning APIs in the C++ front end From: Martin Sebor To: gcc-patches References: <92db3776-af59-fa20-483b-aa67b17d0751@gmail.com> <47d06c821a53f5bd2246f0fca2c9a693bff6b882.camel@redhat.com> <3a5ea83c-0d91-d123-f537-f8f1223df890@gmail.com> Message-ID: Date: Mon, 21 Jun 2021 15:37:21 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_LINKBAIT3, KAM_SHORT, PDS_TONAME_EQ_TOLOCAL_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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, 21 Jun 2021 21:37:23 -0000 Ping: https://gcc.gnu.org/pipermail/gcc-patches/2021-June/571977.html Looking for a review of the C++ front end changes to switch to the new suppress_warning() API. On 6/4/21 3:42 PM, Martin Sebor wrote: > The attached patch replaces the uses of TREE_NO_WARNING in the C++ > front end with the new suppress_warning(), warning_suppressed_p(), > and copy_warning() APIs.