From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code] Date: Wed, 10 Oct 2018 22:50:54 +0200 Message-ID: <87r2gxr0ep.fsf@telefonica.net> References: <638fb7dc-6fc5-4645-8793-97a00038a3a8@googlegroups.com> <8hxojvzzzzzz.m4h.xxuns.g6.gal@portable.galex-713.eu> <20181006192457.GB7368@tuxteam.de> <86lg79yl54.fsf@zoho.com> <86d0slrb4h.fsf@zoho.com> <86d0sknoud.fsf@zoho.com> <86tvlvmxtz.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1539204635 28137 195.159.176.226 (10 Oct 2018 20:50:35 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 10 Oct 2018 20:50:35 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Oct 10 22:50:31 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gALR7-0007CX-0G for geh-help-gnu-emacs@m.gmane.org; Wed, 10 Oct 2018 22:50:29 +0200 Original-Received: from localhost ([::1]:59117 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gALTD-0004Hz-J3 for geh-help-gnu-emacs@m.gmane.org; Wed, 10 Oct 2018 16:52:39 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42930) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gALRj-0003r7-P1 for help-gnu-emacs@gnu.org; Wed, 10 Oct 2018 16:51:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gALRg-0003c8-GT for help-gnu-emacs@gnu.org; Wed, 10 Oct 2018 16:51:07 -0400 Original-Received: from [195.159.176.226] (port=47498 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gALRg-0003bw-9d for help-gnu-emacs@gnu.org; Wed, 10 Oct 2018 16:51:04 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1gALPX-0005EO-Cg for help-gnu-emacs@gnu.org; Wed, 10 Oct 2018 22:48:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 11 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:7wIu3E97xI9s7od6msi0k4ks9+w= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:118249 Archived-At: Barry Margolin writes: > If a function is "insanely long" then inlining will have negligible > effect. Funcall overhead is only relevant if the function is really > short, so it spends nearly as much time calling the function as doing > the actual work of the function, AND you call the function frequently > enough that this overhead adds up to something significant. Inlining is not only about funcall overhead, although most compilers use code length as the unique heuristic for deciding when to inline a function.