From: Alex <agrambot@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, 24720@debbugs.gnu.org
Subject: bug#24720: Performance impact of -no-pie
Date: Tue, 18 Oct 2016 22:41:02 -0600 [thread overview]
Message-ID: <87funtt0gx.fsf@gmail.com> (raw)
In-Reply-To: <rtd1ixr6lo.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 18 Oct 2016 11:59:15 -0400")
Glenn Morris <rgm@gnu.org> writes:
> All that adding -no-pie does is restore the old default behaviour.
> It therefore makes no sense for it to cause a slowdown.
That makes sense.
> I'm going to guess that when you set it via CFLAGS, you lost the -O2
> that is otherwise part of the default CFLAGS.
That's indeed the case. I thought that specifying it when calling
./configure would have just added to the default CFLAGS instead of
overwriting it. Sorry for the false report.
> M-x report-emacs-bug includes information that would probably have
> made this obvious from the outset. Check the setting of CFLAGS in
> src/Makefile.
No, without specifying any CFLAGS manually, report-emacs-bug doesn't
mention any configuration details. This appears to be because
system-configuration-options is empty in that case.
Only when manually specifying flags does report-emacs-bug show the
configuration option section.
I can see what the CFLAGS are in src/Makefile, thanks. Though it might
be nice if I could see these at the Elisp level even when they're the
default.
next prev parent reply other threads:[~2016-10-19 4:41 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
2016-10-18 15:59 ` Glenn Morris
2016-10-18 16:21 ` Paul Eggert
2016-10-19 4:41 ` Alex [this message]
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=87funtt0gx.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=24720@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=rgm@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.