From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jimmy Yuen Ho Wong Newsgroups: gmane.emacs.bugs Subject: bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings Date: Sat, 6 May 2023 17:52:35 +0100 Message-ID: References: <83ild6j4k9.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000040cad05fb093e99" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22690"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 63302@debbugs.gnu.org, Andrea Corallo To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat May 06 18:54:17 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 1pvLAn-0005ea-KJ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 06 May 2023 18:54:17 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pvLAa-0002xD-B3; Sat, 06 May 2023 12:54:04 -0400 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 1pvLAZ-0002wy-4r for bug-gnu-emacs@gnu.org; Sat, 06 May 2023 12:54:03 -0400 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 1pvLAY-0006tX-Kg for bug-gnu-emacs@gnu.org; Sat, 06 May 2023 12:54:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pvLAY-0006wX-D6 for bug-gnu-emacs@gnu.org; Sat, 06 May 2023 12:54:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jimmy Yuen Ho Wong Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 06 May 2023 16:54:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63302 X-GNU-PR-Package: emacs Original-Received: via spool by 63302-submit@debbugs.gnu.org id=B63302.168339200626642 (code B ref 63302); Sat, 06 May 2023 16:54:02 +0000 Original-Received: (at 63302) by debbugs.gnu.org; 6 May 2023 16:53:26 +0000 Original-Received: from localhost ([127.0.0.1]:35676 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pvL9y-0006ve-5S for submit@debbugs.gnu.org; Sat, 06 May 2023 12:53:26 -0400 Original-Received: from mail-qv1-f44.google.com ([209.85.219.44]:59780) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pvL9u-0006vP-W6 for 63302@debbugs.gnu.org; Sat, 06 May 2023 12:53:24 -0400 Original-Received: by mail-qv1-f44.google.com with SMTP id 6a1803df08f44-619be7d7211so14097576d6.3 for <63302@debbugs.gnu.org>; Sat, 06 May 2023 09:53:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683391997; x=1685983997; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=swpxnehJF5uvPa9EkFRUcRsLWZr9yUqqrVGM64/e9O0=; b=r3CNemlVu8Gc759eIfyLLOLHAfZqP1WZNVP0rl7AOu4GhoqVoepx7Hp7A4ja2R9o// T2LnvFfaX3F++Zkvo9Qyde+0s+QbuFJ18arAM7wf30XjVOY6l802OYT8/xgUGqWwxsR6 Q1I1wrVoW6EHBeP9x2V2wEAShDCTkSVdoFvynkosGotmN0NTX3ciijibcMOBQ6ccnGEt k69Br9FqcXnsgYScKFDNEBZfWPCAx47YQ4ZHXMQHSHTh1fpQ5LAfyynx3Rs5sg87NvFb eV0UFtfPEqYUuk2T06ui7aJhBVa0zFCHmnsFGGeqIpfdogfXZJf8U0cHyqF/CyXkgu6/ HYWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683391997; x=1685983997; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=swpxnehJF5uvPa9EkFRUcRsLWZr9yUqqrVGM64/e9O0=; b=jK8Rf9268b6SmBrp6l7T5nxrrZ/dz7vUbQfxnUQqkAMQo/u6+18GkG/wl74EaashyC 6JZyDnphGxsLZvt4k+ct6F1FJS2FuYeBRBLAY/ZI0lvBzomUry5EjQJpl+zw10tCLwqY S3a7hdyJk+5Ywo6ZSYkIM1U71EZnM7BxfEqo146XH16841N8MKa5Tr0H91MyDRz8E+aH mZoy0HCJHBW8OjCr8SHv0ngT/NvVa5k9kCMG3ix6qIIr+DxQlkc+pZsepfiFgwJpbc/G taLibSXfqGUlrhax3AmREl8xwt5pCw4TZ0QtIbz4xbpGMLU5c1DlXFZ6wriwxQg7E6WQ UdkA== X-Gm-Message-State: AC+VfDwz3tfT6IrLVjZbp0UOCbHoT0mtUiVN+F9yNstG/XhXTEAadjea h7zqvB4tJ7U0Nc+6JIwpqfnmcODxm147X7NB8us= X-Google-Smtp-Source: ACHHUZ6S6j/+7m1c1VZPi/rb36I24nauICbFZVIRCysiog6NDVl1Tr1lCG3LGuAOkuaMV8VKXQawJVln0F4mE9JmySc= X-Received: by 2002:a05:6214:509b:b0:5ef:4de6:c4f4 with SMTP id kk27-20020a056214509b00b005ef4de6c4f4mr6603549qvb.15.1683391997282; Sat, 06 May 2023 09:53:17 -0700 (PDT) In-Reply-To: <83ild6j4k9.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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:261203 Archived-At: --000000000000040cad05fb093e99 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Yes I'm talking about nativecomp. Reproduction: 1. (setq package-native-compile t) 2. (setq byte-compile-warnings '(not docstrings docstrings-non-ascii-quotes)) 3. (setq native-comp-async-report-warnings-errors 'silent) 4. M-x package-install ov 5. Observe the differences between the *Compile-Log* buffer and the *Warnings* buffer. Jimmy On Fri, May 5, 2023 at 2:22=E2=80=AFPM Eli Zaretskii wrote: > > From: Jimmy Yuen Ho Wong > > Date: Fri, 05 May 2023 12:51:47 +0100 > > > > > > `byte-compile-warnings` is commonly set to to remove `docstring` so > > spurious `docstring wider than 80 characters` are removed. When it is > > set to such a way, normal byte compilation of a el file with a docstrin= g > > longer than 80 characters will not result in the above warning, but > > natively compiling the same file will. > > > > The expectation should be that nativecomp respects this variable at the > > very least, or that the linting capabilities is moved out of byte > > compilation into a seperate package ala elisp-lint. A compiler should > > compile any program that is valid without producing any warnings except > > obsolete/deprecations. > > Please show a recipe for reproducing this warning from native > compilation. > > I suspect that you are talking about JIT native-compilation, which > happens in a separate Emacs process, in which case we need a way of > injecting settings into that separate process to suppress warnings > selectively, or for doing any other similar jobs. Seeing a recipe for > reproducing this will confirm or contradict my guess. > > Andrea, any comments? > --000000000000040cad05fb093e99 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes I'm talking about nativecomp.

Reproduc= tion:

1. (setq package-native-compile t)
2. (se= tq byte-compile-warnings '(not docstrings docstrings-non-ascii-quotes))=
3. (setq native-comp-async-report-warnings-errors 'silent)4. M-x package-install ov
5. Observe the differences between th= e *Compile-Log* buffer and the *Warnings* buffer.


Jimmy


=
On Fri, Ma= y 5, 2023 at 2:22=E2=80=AFPM Eli Zaretskii <eliz@gnu.org> wrote:
> From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
> Date: Fri, 05 May 2023 12:51:47 +0100
>
>
> `byte-compile-warnings` is commonly set to to remove `docstring` so > spurious `docstring wider than 80 characters` are removed.=C2=A0 When = it is
> set to such a way, normal byte compilation of a el file with a docstri= ng
> longer than 80 characters will not result in the above warning, but > natively compiling the same file will.
>
> The expectation should be that nativecomp respects this variable at th= e
> very least, or that the linting capabilities is moved out of byte
> compilation into a seperate package ala elisp-lint. A compiler should<= br> > compile any program that is valid without producing any warnings excep= t
> obsolete/deprecations.

Please show a recipe for reproducing this warning from native
compilation.

I suspect that you are talking about JIT native-compilation, which
happens in a separate Emacs process, in which case we need a way of
injecting settings into that separate process to suppress warnings
selectively, or for doing any other similar jobs.=C2=A0 Seeing a recipe for=
reproducing this will confirm or contradict my guess.

Andrea, any comments?
--000000000000040cad05fb093e99--