From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.bugs Subject: bug#46670: 28.0.50; [feature/native-comp] possible miscompilation affecting lsp-mode Date: Sun, 28 Feb 2021 08:14:24 +0000 Message-ID: References: <87a6ry46uc.fsf@collares.org> <83mtvqpp15.fsf@gnu.org> <835z2eosqn.fsf@gnu.org> <83v9adolkk.fsf@gnu.org> <83o8g5ocyu.fsf@gnu.org> <834khxnykt.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37800"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 46670@debbugs.gnu.org, mauricio@collares.org, Andrea Corallo To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Feb 28 09:16:14 2021 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 1lGHFN-0009j2-NG for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 28 Feb 2021 09:16:13 +0100 Original-Received: from localhost ([::1]:39490 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lGHFM-0003eH-B2 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 28 Feb 2021 03:16:12 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39992) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lGHFC-0003eA-4e for bug-gnu-emacs@gnu.org; Sun, 28 Feb 2021 03:16:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34250) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lGHFB-0001Bq-Tf for bug-gnu-emacs@gnu.org; Sun, 28 Feb 2021 03:16:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lGHFB-0000Px-N2 for bug-gnu-emacs@gnu.org; Sun, 28 Feb 2021 03:16:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 28 Feb 2021 08:16:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46670 X-GNU-PR-Package: emacs Original-Received: via spool by 46670-submit@debbugs.gnu.org id=B46670.16145001081534 (code B ref 46670); Sun, 28 Feb 2021 08:16:01 +0000 Original-Received: (at 46670) by debbugs.gnu.org; 28 Feb 2021 08:15:08 +0000 Original-Received: from localhost ([127.0.0.1]:45795 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lGHEK-0000Of-8h for submit@debbugs.gnu.org; Sun, 28 Feb 2021 03:15:08 -0500 Original-Received: from mail-oi1-f180.google.com ([209.85.167.180]:35346) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lGHEJ-0000No-3J for 46670@debbugs.gnu.org; Sun, 28 Feb 2021 03:15:07 -0500 Original-Received: by mail-oi1-f180.google.com with SMTP id i21so12512123oii.2 for <46670@debbugs.gnu.org>; Sun, 28 Feb 2021 00:15:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KM/gk9FXrBhdSHOE5k6Uc3WhexVnaQ8/u/1RRai5F64=; b=j6nBjO+BGcklIBBEJwmyfujpzSAr+5fUsq17uHHoR8JJUu6LGD7QNunC5Pdb7/RNjU fPAwpxZgbKqvpK0ZwVI6EkDsLCpRTTpZLugeRVOz6Ty7ioXPRaWoft4Q2EE+SUFbW7Ii huTEhNttGbySvGXLKSnVdEtJwwHMZyxs1DZ5T3EjwEcq701bZ5304cv7O8L3LCMyB2tR TuBr+vYgzHeU5e/4gINj/EhnWroF3IcSt4ptgvpRwh1moOOtR1x3Rj1E+LnIwXjv13ND pd+DLv+F8LUfEKG5zMiwTQXDFWvgk4IiOa8DWGru0MHqvvW/Nc6EUPXS0UeAthTIDJpk 1iYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KM/gk9FXrBhdSHOE5k6Uc3WhexVnaQ8/u/1RRai5F64=; b=hAR7cfmnSYV1cJLODXhDmU/fv6PsLwvgAtWfvOtrH8LB0LwAA6uNystR1z1iQD/Lre NGPOZUeC1zEeBeRkEpIBJWa/j55uQ0Bo4O8nd5JWW7mVaxQ0L7wdIhrsZY0eR6DH5ssP Z7JsAeSFQ3wLftq85YHvozFcSzUTF+Bu9N+lRh+aE7EXK+L+1qb34FBRg8++Zw8/+2yR tbHMNVp+LKDOttLPGhkYT4M2L69hPifi9+dXnlFCR0vKC0paHhjVrO50cPJ7CB6vROuy VvHQQ2opx04osE7tIqLaNbHwTi90URBqCriojzngMJP2sj2/WqwwEy+X7huewT6HShbe Tprw== X-Gm-Message-State: AOAM532Dpjh5iHGqj7AegYNmTRWAgWeeUia4N/c+6HCpiiB7T7wTz8Sd jhcthYOhi6ygiZzj0vESuDCt05+N97+yPW7cFCw= X-Google-Smtp-Source: ABdhPJx1XUel5Fv82Uz9CyAsfXTSIQe18q0ZhYGqSjziSuZNJPKeP0pt03zM9DWLCsjB8u/l3rydc8/GyHGxxiASK+Q= X-Received: by 2002:aca:4c5:: with SMTP id 188mr7748351oie.44.1614500101345; Sun, 28 Feb 2021 00:15:01 -0800 (PST) In-Reply-To: <834khxnykt.fsf@gnu.org> 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" Xref: news.gmane.io gmane.emacs.bugs:201012 Archived-At: On Sat, Feb 27, 2021 at 6:41 PM Eli Zaretskii wrote: > > I take it you've read through the code, understood it all, and > > concluded the reasons were "sound", then? > > I have my own ways of judging what people say and deciding when they > are sound and when they aren't. If you want to question my judgment > as well, you are talking to the wrong guy. You're using "sound" to mean "superficially correct". I understood it to have its mathematical (and legal) meaning, "irrefutably correct". > > I have my own opinions about why Emacs attracts so few volunteers and > > drives away so many of those who might be. > > You are welcome to step up to be the Emacs maintainer, and then act > according to your opinions. There's a whole spectrum between "we shouldn't fly into that mountain" and "let me take the controls". > > > What matters to me at this point is the end result. > > > Any issue that > > > causes mis-compilation of Lisp programs should be fixed, of course. > > > Issues that don't affect the natively-compiled code are much less > > > important, and as I explained, my tendency is to accept Andrea's > > > judgment on those. > > > > There's a difference between "this issue doesn't affect > > natively-compiled code" (which makes it a non-issue, case 2 above) and > > "we don't know whether this issue affects natively-compiled code" > > (which emphatically does not, case 3 above). Evidence of absence and > > all that. > > When there's evidence, there's no doubt, and such issues should be and > are taken care of. Where there's no evidence, we trust the judgment > of the best experts we have, when they show (as they usually do) they > carefully considered the issue before expressing their opinions. The > rest of us, if we don't agree with the expert judgment, get to work > harder to find the evidence. There's no way around this. Let's see how this plays out.