From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Emacs:Native-Comp Backtrace Date: Wed, 26 Aug 2020 19:09:01 +0000 Message-ID: References: <24389.44700.121870.344164@google.com> Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28173"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) Cc: emacs-devel@gnu.org To: "T.V Raman" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 26 21:10:02 2020 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 1kB0o5-0007Al-3g for ged-emacs-devel@m.gmane-mx.org; Wed, 26 Aug 2020 21:10:01 +0200 Original-Received: from localhost ([::1]:49948 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kB0o4-00016F-47 for ged-emacs-devel@m.gmane-mx.org; Wed, 26 Aug 2020 15:10:00 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36916) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kB0nC-0008Uu-Dz for emacs-devel@gnu.org; Wed, 26 Aug 2020 15:09:07 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:50290) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kB0n9-0004FB-Ud for emacs-devel@gnu.org; Wed, 26 Aug 2020 15:09:06 -0400 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 07QJ91Oo010664; Wed, 26 Aug 2020 19:09:01 GMT In-Reply-To: (T. V. Raman's message of "Wed, 26 Aug 2020 08:06:27 -0700") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/26 15:09:02 X-ACL-Warn: Detected OS = ??? 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.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:254253 Archived-At: "T.V Raman" writes: > "T.V Raman" writes: > > Here is some more info based on a work-around: > > Conjecture: native-comp has issues with with-eval-after-load and > friends: > > The following setup produced the afore-mentioned error: > > 1. In the emacs startup, load dired-x when dired is loaded: > (with-eval-after-load "dired" (require 'dired-x)) > 2. dired-mode-hook contains dired-omit-mode defined in dired-x > 3. During startup, a dired buffer is opened -- either via psession, > desktop or some other means > > With the above, you get the error (symbol's function definition is > void: dired-omit-mode) > > Fix: If in the startup file, you remove the with-eval-after-load and > simply require dired-x, then it works. > > Additional info which lends credence to the conjecture: > > Emacspeak loads module-specific code using eval-after-load e.g. when > "ido" is loaded, it loads emacspeak-ido after ido is done loading. In > native-comp emacs, I find that (featurep 'emacspeak-ido) is nil after > ido is loaded. > > I suspect use-package may also be affected in a similar way. Hi Raman thanks for having a look. This issue sounds strange but before looking into it I'd like to rework the advicing primitive mechanism for the native code. This is a source of incompatibility that may cause a number of the small strange behaviours we still see today. As a matter of fact today any primitive that gets advised if is not listed in `comp-never-optimize-functions' will misbehave with respect to the vanilla implementation. This should be the last non small area that need intervention and I'll be on this very soon. Andrea -- akrl@sdf.org