From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Manoj Srivastava <srivasta@golden-gryphon.com>,
Dmitry Antipov <dmantipov@yandex.ru>,
17806@debbugs.gnu.org
Subject: bug#17806: 24.4.50; Branch emacs-24 fails to beuild on Debian
Date: Fri, 20 Jun 2014 17:06:19 -0400 [thread overview]
Message-ID: <jwvoaxnmgx8.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <53A48FF2.9000805@cs.ucla.edu> (Paul Eggert's message of "Fri, 20 Jun 2014 12:48:02 -0700")
>> Why does Emacs even have --enable-link-time-optimization as a configure
>> option? Does it provide any measurable benefit?
> It's supposed to have better runtime performance. In my standard little
> benchmark, though, --enable-link-time-optimization slowed down runtime CPU
Don't know what benchmark you use, but I generally use byte-compilation
of Emacs's files as my own benchmark. It's kind of lousy (since it
constantly changes), but it is one real-life code where a lot of Elisp
is executed.
> I installed the attached as emacs-24 bzr 117269 to try to discourage casual
> use. Another possibility would be to
> remove --enable-link-time-optimization, but I suppose that should be done in
> the trunk if it's done at all. I'll CC: this to Dmitry as he added the
> option in the first place.
If it tends to break (and since IIUC it's new in 24.4), we could also
remove it from 24.4.
Stefan
next prev parent reply other threads:[~2014-06-20 21:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 22:37 bug#17806: 24.4.50; Branch emacs-24 fails to beuild on Debian Manoj Srivastava
2014-06-19 2:56 ` Eli Zaretskii
2014-06-19 3:41 ` Glenn Morris
2014-06-19 6:35 ` Manoj Srivastava
2014-06-19 8:42 ` Dmitry Antipov
2014-06-19 17:22 ` Manoj Srivastava
2014-06-19 18:39 ` Sven Joachim
2014-06-20 6:17 ` Paul Eggert
2014-06-20 7:20 ` Eli Zaretskii
2014-06-20 7:56 ` Paul Eggert
2014-06-20 8:15 ` Eli Zaretskii
2014-06-20 17:15 ` Glenn Morris
2014-06-20 19:48 ` Paul Eggert
2014-06-20 21:06 ` Stefan Monnier [this message]
2014-06-20 23:55 ` Paul Eggert
2014-06-21 12:54 ` Stefan Monnier
2014-06-21 3:46 ` Dmitry Antipov
2014-06-21 19:58 ` Glenn Morris
2014-06-24 14:56 ` Dmitry Antipov
2014-06-24 16:27 ` Paul Eggert
2014-06-24 16:39 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvoaxnmgx8.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17806@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=srivasta@golden-gryphon.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).