From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) by sourceware.org (Postfix) with ESMTPS id 06B593943425 for ; Mon, 21 Jun 2021 21:35:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 06B593943425 Received: by mail-oi1-x235.google.com with SMTP id x196so21469810oif.10 for ; Mon, 21 Jun 2021 14:35:39 -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:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=YYAUxcswyC9Zhnd6Wxr/WZ2NVxLyxV2VrYIPWL4CWI4=; b=prKEOEzwmTxf4N8SlOUJeyG13pz/kDBZHbb8TfRv6GiLxrNBoVMAO2BsAT02fMl6Y0 zbaCkrYj6GF3FxPOuizw+5D2d/qzEPVJhZyZucATIlgsAF7Z5TlpcuLyPjfHSK8BW896 DNbSgc3pNQ/JiK4ixjP0b9+DhudPgVhzIulFjYB6QvLrbKrgcfYoB/L0t8iFpCudUM7D bsDTf3Pcreyjgd/wNiMTlvOnOX1Wsn8d2i2oEPM30vsbhoeUO23lxixXkxAWb4FVe/Ry 0ANRvwlbXPuQWsW9cqpjUOqzqA/PLXdyU6FXXhVupVlxVqFEVRIm2P76wu/rNorQyRMQ V8vQ== X-Gm-Message-State: AOAM530khLpTVtYK9crLbgIY9UDkevqgxZKYepBWApdDVlz+eXFmoywr xyTRbSELDgXkZb3Nb3W7B5Y= X-Google-Smtp-Source: ABdhPJymWXzmnNOklestlWO9Kd0xI/whul7HtyXwue5uNDDFrOEPdLUVx+Z8oxASbu21s+X/w6aJYg== X-Received: by 2002:a05:6808:ce:: with SMTP id t14mr551903oic.29.1624311338515; Mon, 21 Jun 2021 14:35:38 -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 y18sm1490056oiv.46.2021.06.21.14.35.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Jun 2021 14:35:38 -0700 (PDT) Subject: [PING][PATCH 4/13] v2 Use new per-location warning APIs in C family code From: Martin Sebor To: gcc-patches , Jason Merrill , "Joseph S. Myers" References: <92db3776-af59-fa20-483b-aa67b17d0751@gmail.com> <47d06c821a53f5bd2246f0fca2c9a693bff6b882.camel@redhat.com> <3a5ea83c-0d91-d123-f537-f8f1223df890@gmail.com> <613b4fc4-4bf0-c226-15a9-b1fd4ccd9c8e@gmail.com> Message-ID: Date: Mon, 21 Jun 2021 15:35:37 -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: <613b4fc4-4bf0-c226-15a9-b1fd4ccd9c8e@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.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:35:40 -0000 Ping: https://gcc.gnu.org/pipermail/gcc-patches/2021-June/571975.html I'm looking for a review of the mostly mechanical shared subset of the C and C++ front end changes 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 shared > C family front end with the new suppress_warning(), > warning_suppressed_p(), and copy_warning() APIs.