all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: emacs-devel@gnu.org
Cc: Daniel Colascione <dancol@dancol.org>
Subject: Re: Inlining doesn't happen on OS X: big performance problem
Date: Thu, 19 Sep 2013 08:06:03 -0700	[thread overview]
Message-ID: <523B12DB.9000305@cs.ucla.edu> (raw)
In-Reply-To: <523AFFBA.3080305@cs.utoronto.ca>

Ryan Johnson wrote:
> Surely something that elaborate and costly was a conscious decision...

Yes, that's correct.  As noted in the code's comments,
the problem is that Apple's C library is incompatible with
C99; see the thread here:

http://lists.gnu.org/archive/html/bug-gnulib/2012-12/msg00023.html

This is registered as Darwin bug 12841334, whatever that is (I don't
have access to the Apple bug database).  As I understand it, it
it's a nontrivial bug, involving only the C library
headers but also clang (the default C compiler used by Apple).
I've corresponded with a developer at Apple about this (most recent
correspondence August 21), and as I understand it Apple plans to
fix the bug at some point, but the fix isn't public yet.  When it
is, I'd like to adjust Gnulib so that it avoids the problem on
fixed versions of Darwin.

In reviewing that correspondence I think that we could work
around some cases of the problem by replacing both instances of
'defined __APPLE__' with this:

    (defined __APPLE__ \                                                        
     && ! (defined _DONT_USE_CTYPE_INLINE_ \
           && ! (defined _FORTIFY_SOURCE && _FORTIFY_SOURCE)))

in m4/extern-inline.m4.  This would improve performance if you
compile Emacs with -D_DONT_USE_CTYPE_INLINE_ -D_FORTIFY_SOURCE=0.
If you're interested in building Emacs that way
I can make that change to Gnulib.



  reply	other threads:[~2013-09-19 15:06 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
2013-09-19 15:06   ` Paul Eggert [this message]
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=523B12DB.9000305@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=dancol@dancol.org \
    --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.