From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) by sourceware.org (Postfix) with ESMTPS id 7EF7E3861830 for ; Mon, 21 Jun 2021 21:42:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7EF7E3861830 Received: by mail-ot1-x332.google.com with SMTP id h24-20020a9d64180000b029036edcf8f9a6so19256692otl.3 for ; Mon, 21 Jun 2021 14:42:16 -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=LQCNIhMAoK9Hvl/pwfL6dLvKbUZgwimL7k8GWBLcjdY=; b=iWyes24nBA0jdK8Nyj+IZu7qZ/H0q/gYoOcdoWcKLgkv5BFDV8263XLnd5BEwUIeSp 1DwvHktaxJTLh05sJkhVQU8L0LeRBA4or8t05Cm1Enr8aHFZEw1/MxYRyHvo0zkRUSfW FJ64LzFyh9OLKDTd15rtOV6qls3t8rqkkFRmN0pJziefsumsnOMJbCd7NbeDnzGGDzuF V9YxJvrM4USgSeCXL2B76mjiIbXsM3Lht2g8il9xxAzNiZ1gUK3bRLyceYNDDhrjt2Oa NcUyIh31daNlU6dH1cu8Sc6dPMe1qjGOsQXRrvWXLHRE+xOLCSpaM2C63uYepfeo9aDh FJPw== X-Gm-Message-State: AOAM531l1+ByNs4sUk62Wk3h5dcmgSnpSyWCQ7r02t91IALtYFqHIMtn ww2Q5OXjPVVyGPGMmcQsIwBlcHJHc4M= X-Google-Smtp-Source: ABdhPJxnmW+0+mldbHq5Mh2k8S/hzDbMmw03pz2zHcfWaen3BoN07YIMT61oKuO4olYAk2s846rc/g== X-Received: by 2002:a9d:82b:: with SMTP id 40mr148641oty.81.1624311735679; Mon, 21 Jun 2021 14:42:15 -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 r7sm264028otn.29.2021.06.21.14.42.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Jun 2021 14:42:15 -0700 (PDT) Subject: [PING][PATCH 7/13] v2 Use new per-location warning APIs in the FORTRAN 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: <064cd9bd-9c8e-9f70-6a84-f2e8583c3b78@gmail.com> Date: Mon, 21 Jun 2021 15:42:14 -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.1 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:42:20 -0000 Ping: https://gcc.gnu.org/pipermail/gcc-patches/2021-June/571978.html Looking for an approval of the 99% mechanical changes to switch the FORTRAN front end from TREE_NO_WARNING to the new suppress_warning() API. There's only one place in this patch where a specific warning is being suppressed -Wuninitialized. All other calls suppress all warnings as before, so I don't expect the patch to have any visible changes. On 6/4/21 3:42 PM, Martin Sebor wrote: > The attached patch replaces the uses of TREE_NO_WARNING in the FORTRAN > front end with the new suppress_warning() API.