From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Getting ready to land native-compilation on master Date: Wed, 14 Apr 2021 10:50:45 -0400 Message-ID: References: <83v98v7dzs.fsf@gnu.org> <87y2dl9p2k.fsf@posteo.net> <878s5l9msq.fsf@posteo.net> <83zgy1ywja.fsf@gnu.org> <874kg99g6v.fsf@posteo.net> <83r1jdyptp.fsf@gnu.org> <87k0p5c6ep.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11828"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Philip Kaludercic , emacs-devel@gnu.org, Eli Zaretskii , akrl@sdf.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 14 16:51:58 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 1lWgs2-0002wF-40 for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Apr 2021 16:51:58 +0200 Original-Received: from localhost ([::1]:39752 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lWgs1-0006WM-2o for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Apr 2021 10:51:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47446) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lWgqz-0005Hh-Su for emacs-devel@gnu.org; Wed, 14 Apr 2021 10:50:53 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:3203) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lWgqx-00009N-6j; Wed, 14 Apr 2021 10:50:52 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 18D9780379; Wed, 14 Apr 2021 10:50:49 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 7195C8081F; Wed, 14 Apr 2021 10:50:47 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1618411847; bh=jBO55pT/2TzJgkYhoWAcdLckZQU2TMTOSl2x2rWFxjc=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=mISqKGdpZ59i2raAEYj4VGxcWOoCPQUiZ0olpRI9NLM88Icx93dDPvjM95Xbpxde2 UxSr8Do3IKySsWx3E0Q6wW81Qb9/4PAlnd1wvPt9DTaO3V3PpN8qBUFeCmbmytEvbb wROAHqQmNFQJgkKz9vbjhWbnw3i2LKIihdlnG0SCe1DAzeGpYiIHe6tPr8T9EzE/YJ knm7HZ8LASqX+sm3qbAAbppbslZu7HHlrFKEN9Obb8UkYGgLmgBpBo2j7xqrxd58XR u/KI28Z/dO1NjfbA/VC7VMj8Yf7OqCmOeT7v4GC8MGL5zUPbqftNoxEQsXswx5i2Kr kXDhJcWgHA8Jw== Original-Received: from alfajor (104-222-126-84.cpe.teksavvy.com [104.222.126.84]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 1323312025D; Wed, 14 Apr 2021 10:50:47 -0400 (EDT) In-Reply-To: (Stefan Kangas's message of "Wed, 14 Apr 2021 09:35:41 -0500") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=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.23 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:268052 Archived-At: >> The difference being that this is not generated when the package is >> installed, but suddenly appears in a buffer. > > This shouldn't be a problem once we flip > `comp-async-report-warnings-errors' to nil by default. AFAIK, the plan > is to do that in time for Emacs 28. As others have explained, we keep > it set to t for now as it indicates real problems. The warnings mentioned in this thread are those we normally see when we byte-compile the file, which should be a separate step from the async compilation to native code, so AFAICT showing those warnings during native compilation is not very useful (what would be useful would be warnings/info specific to async/native compilation). Stefan