From: Glenn Morris <rgm@gnu.org>
To: 17806@debbugs.gnu.org
Cc: eggert@cs.ucla.edu
Subject: bug#17806: 24.4.50; Branch emacs-24 fails to beuild on Debian
Date: Fri, 20 Jun 2014 13:15:36 -0400 [thread overview]
Message-ID: <fv8uorqz7r.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87ionxaloa.fsf@glaurung.internal.golden-gryphon.com>
Paul Eggert wrote:
> never had much luck with GCC's link time optimization, to be honest --
> crashes and glitches like these seem to happen every time I use it.
Why does Emacs even have --enable-link-time-optimization as a configure
option? Does it provide any measurable benefit? (Apart from "crashes a
lot"? :) ) Should the configure option description add a general warning?
next prev parent reply other threads:[~2014-06-20 17:15 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 [this message]
2014-06-20 19:48 ` Paul Eggert
2014-06-20 21:06 ` Stefan Monnier
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=fv8uorqz7r.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=17806@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 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).