From: Alex <agrambot@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 24720@debbugs.gnu.org
Subject: bug#24720: Performance impact of -no-pie
Date: Mon, 17 Oct 2016 22:06:11 -0600 [thread overview]
Message-ID: <87vawql2rw.fsf@gmail.com> (raw)
In-Reply-To: <2e4bd054-3bed-501a-de51-55216eb2377f@cs.ucla.edu> (Paul Eggert's message of "Mon, 17 Oct 2016 13:26:32 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
>> Is such a performance impact expected? If so, is there a plan to regain the
> old speed?
>
> No, such a performance change is not expected.
>
> Can you reproduce the problem with the emacs-25 or master branches, without
> manually adding -no-pie to CFLAGS? The bleeding-edge versions of Emacs attack
> the problem in a slightly different way, which might affect performance less.
>
> If you still see a performance problem, can you narrow it down, e.g., by
> configuring it with --enable-profiling and seeing where the extra cycles are
> going?
Ah, I see. It looks like the bleeding-edge versions add -no-pie to
LDFLAGS instead of CFLAGS. Doing the same thing myself both to those
versions and the 25.1 tarball (which is what I was using before) now
results in the same performance as before, within error.
Is it a bug that adding -no-pie to CFLAGS slows startup and runtime
performance by a factor of 2?
I would have expected that -no-pie would generally be faster compared to
-pie. Is that not the case?
Thanks.
next prev parent reply other threads:[~2016-10-18 4:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 20:18 bug#24720: Performance impact of -no-pie Paul Eggert
[not found] ` <handler.24720.B.147673554717923.ack@debbugs.gnu.org>
2016-10-17 20:26 ` Paul Eggert
2016-10-18 4:06 ` Alex [this message]
2016-10-18 15:59 ` Glenn Morris
2016-10-18 16:21 ` Paul Eggert
2016-10-19 4:41 ` Alex
2016-10-19 7:04 ` Eli Zaretskii
2016-10-19 19:45 ` Alex
2016-10-20 7:04 ` Eli Zaretskii
2016-10-20 22:13 ` Alex
2016-10-26 4:30 ` Alex
2016-10-18 5:54 ` Cesar Quiroz
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=87vawql2rw.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=24720@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.