From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oo1-xc36.google.com (mail-oo1-xc36.google.com [IPv6:2607:f8b0:4864:20::c36]) by sourceware.org (Postfix) with ESMTPS id 63F13385DC30 for ; Mon, 21 Jun 2021 21:58:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 63F13385DC30 Received: by mail-oo1-xc36.google.com with SMTP id z14-20020a4a984e0000b029024a8c622149so4863021ooi.10 for ; Mon, 21 Jun 2021 14:58:19 -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=IV0ikJeBVTv3k6Wg3P4FwOHEFa7ot8QWLV6rbruSAgM=; b=fM0iFyz2OQ4gGPaulz0LmfqhhYuycieqLsjHn+RAbBLlJ833JKBoiS8jeRHXHt99oc Be1jkD+TetINAO/GAU66dz0SIxWI4gC477aWlxEKt+Qu+Lt2Uyn1LMJSnvxEcsrTsp9E cJEHbcGa2LX/VyJpdUYZ9Dnc4tQVBwGPhtOznrS0YjMxJeLYCSA/c5IbM2NYfCsL1QCx EpCvR7EscKCtO73FpxaBFo8xLN6GnQMlDfV24ZYhOjtNnC5J3rNDMgm5km+/hRh9Tg2E nMydQpZCsGrJaK90pOP0ArkA+/27h7O1N9YgwfbuMsyo9Il0HDUoF39xyV0mgqdL02w/ U8pw== X-Gm-Message-State: AOAM533w2qCAHeZSEeZwQoG7uIlCb74h/GlueC2HyBMYYt0yaYf75NcI k5/yOPUz1lH3Wsu8rEgocHj+IjiVhdk= X-Google-Smtp-Source: ABdhPJxrt5+X+U9sOmBzPuMKUYq3kpnsOG7aNIV0j8J6VlXxlonnd0yFQG2T4LiWJ92By2sKnPp9eA== X-Received: by 2002:a05:6820:315:: with SMTP id l21mr278983ooe.32.1624312698664; Mon, 21 Jun 2021 14:58:18 -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 h2sm76212oog.16.2021.06.21.14.58.18 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Jun 2021 14:58:18 -0700 (PDT) Subject: [PING][PATCH 10/13] v2 Use new per-location warning APIs in the middle 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: <421b5ab6-e360-7308-310b-819b040fe8c5@gmail.com> Date: Mon, 21 Jun 2021 15:58:17 -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=-4.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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:58:20 -0000 Ping: https://gcc.gnu.org/pipermail/gcc-patches/2021-June/571981.html Looking for a review of the middle end changes to replace the uses of TREE_NO_WARNING and gimple_{get,set}_no_warning with the new warning group APIs. Most of the changes are a mechanical search and replace kind, just a handful do ever-so-slightly more than that, but none of those should have any observable effect. On 6/4/21 3:43 PM, Martin Sebor wrote: > The attached patch introduces declarations of the new > suppress_warning(), warning_suppressed_p(), and copy_warning() APIs, > and replaces the uses of TREE_NO_WARNING in the middle end with them.