unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Alex Gramiak <agrambot@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Warnings when building with LTO
Date: Fri, 10 May 2019 00:23:30 -0700	[thread overview]
Message-ID: <6d4d46c8-d11d-976b-7c82-584e1b97021a@cs.ucla.edu> (raw)
In-Reply-To: <87imujckfx.fsf@gmail.com>

On 5/9/19 3:49 PM, Alex Gramiak wrote:
> INSTALL states:
>
>   Link time optimization is not the default as it tends to cause crashes
>   and to make Emacs slower.
>
>
> Is this still true with GCC 9.1?

Not clear. Nobody's really tried it as far as I know. Few people are
using LTO and to some extent it's a chicken-and-egg problem. See, for
example, this recent LTO problem on macOS:

https://lists.gnu.org/r/emacs-devel/2019-05/msg00077.html

for why I still don't recommend using LTO unless your job is to debug LTO.


> Paul, can you still reproduce the
> bug[2] you mentioned in commit 9b4b2e9fc8 with GCC 9.1?
>
>
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1486455

No, it's fixed for me now (Fedora 30 x86-64, 9.1.1 20190503 (Red Hat
9.1.1-1), current master).

I assume that all the warnings you mention are bogus, though I haven't
checked this. It would not be wise to attempt to pacify GCC on all
platforms, as it (1) would take a lot of time and (2) would clutter the
code and get in the way of real work. So we tend to pacify GCC only for
recent GCC with default compiler flags. If LTO becomes the default or is
otherwise commonly used we should pacify the warnings you mention; until
then, I wouldn't bother.




      reply	other threads:[~2019-05-10  7:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 22:49 Warnings when building with LTO Alex Gramiak
2019-05-10  7:23 ` Paul Eggert [this message]

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=6d4d46c8-d11d-976b-7c82-584e1b97021a@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=agrambot@gmail.com \
    --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 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).