From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#61730: 30.0.50; Compiler warnings for delq and delete Date: Mon, 27 Feb 2023 13:44:23 +0200 Message-ID: <835ybnib8o.fsf@gnu.org> References: <87ilfsisje.fsf@web.de> <670D8E4A-333D-4E2D-97CC-86728965989D@gmail.com> <83a613np4p.fsf@gnu.org> <87fsavf688.fsf@web.de> <83k006kvv6.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12894"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 61730@debbugs.gnu.org To: rms@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Feb 27 12:45:32 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pWbwi-0003EJ-9U for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 27 Feb 2023 12:45:32 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pWbwd-00047O-AI; Mon, 27 Feb 2023 06:45:27 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pWbwF-000418-FZ for bug-gnu-emacs@gnu.org; Mon, 27 Feb 2023 06:45:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pWbwF-00078D-5p for bug-gnu-emacs@gnu.org; Mon, 27 Feb 2023 06:45:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pWbwE-0003hG-J5 for bug-gnu-emacs@gnu.org; Mon, 27 Feb 2023 06:45:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 27 Feb 2023 11:45:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61730 X-GNU-PR-Package: emacs Original-Received: via spool by 61730-submit@debbugs.gnu.org id=B61730.167749827014156 (code B ref 61730); Mon, 27 Feb 2023 11:45:02 +0000 Original-Received: (at 61730) by debbugs.gnu.org; 27 Feb 2023 11:44:30 +0000 Original-Received: from localhost ([127.0.0.1]:46260 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pWbvh-0003gF-ON for submit@debbugs.gnu.org; Mon, 27 Feb 2023 06:44:30 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51248) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pWbvg-0003g4-Kv for 61730@debbugs.gnu.org; Mon, 27 Feb 2023 06:44:29 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pWbvb-00070M-EI for 61730@debbugs.gnu.org; Mon, 27 Feb 2023 06:44:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=qbHBv7n63gaYlVPXlFlqbacchGDW2MHwykT4l5ZDoo8=; b=rkHQ2FOcOPq8 wDILD5m+iyko+IyMYfEI/futVxTnNTEDbxLDgd3JvlmWsXgddeMEHQLjm6jZgFvSWXqV256GM9raw L3TsWf9Iir5/U9eiLysay9SbjGzF7ByXa4EwBznwXJBDfwZ89WdOIOi1YRbyXkXOJU5CgmFu4vl3b b1iRTqUdxLQza25GPf0rZ6C+ooOafYO+fZqqABy5y48NCaGaz/GZLwtkI5NcCqTPgsT1klY6qcU6z h8h+PjR03DfEffUz/EJnKt7QmPD7ABG3S6MMamZpOYD/F2yOslCKwP+jwrHWXthcNj8D1teWKxAxe cbiXmihz3K1YPZIkJojibw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pWbvT-0005r7-RU; Mon, 27 Feb 2023 06:44:17 -0500 In-Reply-To: (message from Richard Stallman on Sun, 26 Feb 2023 22:24:27 -0500) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:256871 Archived-At: > From: Richard Stallman > Cc: 61730@debbugs.gnu.org > Date: Sun, 26 Feb 2023 22:24:27 -0500 > > > In Emacs maintenance and development, the two cases are actually one. > > We rebuild Emacs so frequently that even a "rare" warning appears all > > the time and is annoying. It is not a coincidence that we usually > > don't tolerate warnings during the build of Emacs. > > I am surprised -- I didn't do that when I was the main maintainer. We have more branches than back then. I routinely build 3 branches every day -- master, the release branch, and a feature branch for some long-living feature. I build 3 more branches weekly. So I see the same or similar warnings more than once each day. The situations where many Lisp files need to be recompiled are also more frequent nowadays, due to a much more massive use of macros. These reasons add up. > In recent years, ISTR seeing warnings in the build often enough. You are tracking the master branch, which is by definition less clean wrt warnings. > I resent it when a compiler takes up my time pressuring me to prove to > it that I know something isn't a bug, and I usually tell that compiler > (inside my head) where it can take those warnings. Likewise. Although the place I use (in my head) is called by a somewhat different name. But is similar in nature. > When I implemented the options that enable such warnings in GCC, I > urged people NOT to use those options by default. To enable them by > default in a makefile is to impose systematic harassment on every > contributor to the code. You end up with a program as your > taskmaster, haranguing you continually to insert proof that you didn't > make some mistake. Sadly, that stance is all but gone nowadays: compilers, including GCC, wine too much, especially if you use "-Wall", and many projects use "-Wall" by default. That is called "progress". End of rant.