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 compilation on as default? Date: Mon, 20 Nov 2023 04:41:05 -0500 Message-ID: References: <83legs281v.fsf@gnu.org> <83r0liiy44.fsf@gnu.org> <838r7qhtdc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11174"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: stefankangas@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Nov 20 10:41:54 2023 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 1r50mw-0002lQ-EP for ged-emacs-devel@m.gmane-mx.org; Mon, 20 Nov 2023 10:41:54 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r50mB-0005dZ-9i; Mon, 20 Nov 2023 04:41:07 -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 1r50mA-0005cH-KR for emacs-devel@gnu.org; Mon, 20 Nov 2023 04:41:06 -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 1r50mA-0001D7-Bx; Mon, 20 Nov 2023 04:41:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=hchukCIwWdSIzFu5DPhyt6o55AlaEagCOiUEl1zR3SE=; b=KymzC3uhZPQzwl8gcqR6 nQ/qu3Pr0bgJUxQJCZJXKFtod+6PsrXGfQPVmmPNY2Vcc5tJdpRrivftIailEeFUzs/4w/wtGbl59 9tefVsFn7kp2Ub9qysb48sxVGZrTFCljMKAWwvMtmhjBG8nUibw6qNQvpXW7C8uN+E0A9hwbt5DCb j3fG5YQwwNw+Q974hF9r7v499MSZ025KcJ8EHnPSXXghTZ3gidFZho2mKcLVs+eVh6LX3ocuXuhp8 k4xQ1ktGe4diCZDXbKhnOzMFucWlYdz7+6Pr8XkbLlMWfI8IUBpU1pKeS4THG1aXXMyPbZNPofKBz KvR+vjoh34h8Yw==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1r50m9-0005op-VX; Mon, 20 Nov 2023 04:41:05 -0500 In-Reply-To: <838r7qhtdc.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 26 Oct 2023 07:58:55 +0300") 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313040 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: Eli Zaretskii , emacs-devel@gnu.org >> Date: Wed, 25 Oct 2023 16:50:17 -0400 >> >> So I think we could have a new mode, still controlled by >> native-comp-async-report-warnings-errors, that filters out all the >> uninteresting warnings (that the programmer already got during byte >> compilation) but still report this important one. >> >> So even if the package developer doesn't use native compilation it can >> get the bug report for the issue. >> >> I suspect this might be a good compromise/solution. >> >> WDYT? > > Sounds like a plan to me, thanks. While adding this entry in TODO came to my mind this thread. What is the the outcome? Are we fine in activating native comp by default when libgccjit is available? Thanks Andrea