all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: emacs-devel@gnu.org
Subject: Re: Inlining doesn't happen on OS X: big performance problem
Date: Thu, 19 Sep 2013 09:44:26 -0400	[thread overview]
Message-ID: <523AFFBA.3080305@cs.utoronto.ca> (raw)
In-Reply-To: <523AFDA5.4030607@dancol.org>

On 19/09/2013 9:35 AM, Daniel Colascione wrote:
> Currently, gnulib converts "inline" to "static" on OS X. In particular,
> config.h uses this logic from m4/extern-inline.m4:
>
> #if ((__GNUC__ \
>        ? defined __GNUC_STDC_INLINE__ && __GNUC_STDC_INLINE__ \
>        : (199901L <= __STDC_VERSION__ \
>           && !defined __HP_cc \
>           && !(defined __SUNPRO_C && __STDC__))) \
>       && !defined __APPLE__)
> ...
> #elif (2 < __GNUC__ + (7 <= __GNUC_MINOR__) && !defined __STRICT_ANSI__ \
>         && !defined __APPLE__)
> ...
> #else
> # define _GL_INLINE static _GL_UNUSED
> # define _GL_EXTERN_INLINE static _GL_UNUSED
> #endif
>
> Using "static" for "inline" comes at a tremendous cost in performance.
> Compiling with gcc 4.2.1 -O2, Emacs HEAD takes 113.9 seconds to
> font-lock-fontify-buffer lisp.h ten times. If I replace "!defined
> __APPLE__" with "1" above, Emacs compiles and runs perfectly well
> (albeit with some warnings about missing declarations) and performs the
> same task in only 36.8 seconds. Disassembly confirms that in the current
> configuration, nothing is actually being inlined.
>
> Can we please remove these "!defined __APPLE__" tests and start inlining
> functions again in OS X?
>
Surely something that elaborate and costly was a conscious decision... 
have you looked through the revision history to see why this was added 
in the first place? (The hope is that the reason is no longer valid and 
the change can be reverted)

Ryan




  reply	other threads:[~2013-09-19 13:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 13:35 Inlining doesn't happen on OS X: big performance problem Daniel Colascione
2013-09-19 13:44 ` Ryan Johnson [this message]
2013-09-19 15:06   ` Paul Eggert
2013-09-19 21:41     ` Paul Eggert
2013-09-20  1:47       ` Daniel Colascione
2013-09-20  4:24         ` Paul Eggert
2013-09-19 16:35 ` Andreas Schwab
2013-09-19 20:58   ` Daniel Colascione
2013-09-19 21:04     ` Andreas Schwab
2013-09-19 21:11       ` Daniel Colascione
2013-09-19 21:15         ` Andreas Schwab
2013-09-19 21:19         ` Óscar Fuentes
2013-09-19 21:18     ` Paul Eggert
2013-09-19 22:35       ` Ryan Johnson
2013-09-19 22:57         ` Paul Eggert
2013-09-20  2:35           ` Ryan Johnson
2013-09-20  6:14       ` Jan Djärv
2013-09-20  8:15         ` Dmitry Antipov
2013-09-20 14:17           ` Stefan Monnier
2013-09-20 15:37             ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=523AFFBA.3080305@cs.utoronto.ca \
    --to=ryan.johnson@cs.utoronto.ca \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.