From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: native-comp-async-report-warnings-errors default value Date: Fri, 24 Dec 2021 09:53:13 +0000 Message-ID: References: <87h7dj7su7.fsf@gmail.com> <83r1cnlu6y.fsf@gnu.org> <87czo77rx7.fsf@gmail.com> <837dcmamt2.fsf@gnu.org> <83v90694ka.fsf@gnu.org> <83v901zdh6.fsf@gnu.org> <83k0g3cagl.fsf@gnu.org> <8ea45edf-0bd2-a9b4-2341-e08446ea9965@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31952"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel@gnu.org, Stefan Kangas , rpluim@gmail.com To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 24 10:54:33 2021 Return-path: Envelope-to: ged-emacs-devel@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 1n0hHV-0008AO-L7 for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Dec 2021 10:54:33 +0100 Original-Received: from localhost ([::1]:59204 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n0hHT-0007SR-8I for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Dec 2021 04:54:32 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48118) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n0hGM-0006ln-Lw for emacs-devel@gnu.org; Fri, 24 Dec 2021 04:53:22 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:56732) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n0hGK-0005GZ-Ot; Fri, 24 Dec 2021 04:53:22 -0500 Original-Received: from ma.sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 1BO9rDXe024221 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Fri, 24 Dec 2021 09:53:13 GMT In-Reply-To: <8ea45edf-0bd2-a9b4-2341-e08446ea9965@yandex.ru> (Dmitry Gutov's message of "Fri, 24 Dec 2021 03:01:10 +0200") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:283112 Archived-At: Dmitry Gutov writes: > Hi Andrea, > > On 20.12.2021 11:29, Andrea Corallo wrote: >> Stefan Kangas writes: >>=20 >>>> Eli Zaretskii writes: >>>> >>>>> When I said "by popular demand", I meant that. Just your own voice is >>>>> not enough, IMO. >>> >>> I have now reviewed this thread, and changing the default from nil to >>> silent has the support from Robert Pluim, Stefan Kangas, Lars >>> Ingebrigtsen, Andrea Corallo and =C3=93scar Fuentes (5). >>> >>> For keeping the current default I count Eli Zaretskii (1). >>> >>> Neutral in this thread are T.V. Raman and Stefan Monnier (2). >> FWIW please count me on the neutral side, I've no formed opinion on >> this >> ATM even if the more time is passing the more I tend to think that the >> current default might be safer and/or beneficial on the long run. > > This might be a distracting aside, but could you comment on the idea > that I think Stefan mentioned previously: that the native compiler > could use not the original source files, but the byte-compiled *.elc > files as the "source". By the time those are compiled, all the > dependencies are resolved one way or another, right? So the user won't > need to suffer the same kind of warnings again. > > Do they contain the necessary information to do native-compile, and > its various optimizations? If yes, are there any other difficulties > associated with such an approach? Hi Dmitry, this is not a trivial modification so I might easily miss some aspects of it but... Certanly bytecode ATM has no way to store declaration specifiers and these are used for native compilation. I guess we should at least extend this first. BR Andrea