From: Paul Eggert <eggert@cs.ucla.edu>
To: StrawberryTea <look@strawberrytea.xyz>, Eli Zaretskii <eliz@gnu.org>
Cc: 69689@debbugs.gnu.org
Subject: bug#69689: 30.0.50; cannot native compile with -flto in native-comp-compiler-options
Date: Sun, 10 Mar 2024 14:08:48 -0700 [thread overview]
Message-ID: <d6d5d7dd-0b75-4b40-8b0e-90d047f0aaae@cs.ucla.edu> (raw)
In-Reply-To: <87v85ugfh2.fsf@strawberrytea.xyz>
On 2024-03-10 10:32, StrawberryTea wrote:
> Well, I wanted to ask here because I wanted to check if anyone else is
> able to compile elisp files with -flto in native-comp-compiler-options.
> I believe that the error is related to the native-comp branch, as a
> Gentoo developer
Google searches suggest that "plugin needed to handle lto object" is an
issue that arises in Gentoo builds of other projects. The basic issue is
that if you're going to build everything from scratch, you must build
the infrastructure correctly first, and that can include linker plugins.
Sorry I can't help more, as I don't use Gentoo.
On 2024-03-09 22:24, Eli Zaretskii wrote:
> Paul, does Emacs even support -flto builds?
Yes, with './configure --enable-link-time-optimization'. This should
work fine, although the build time is greater and there are a few
false-alarm warnings from GCC - at least they were false alarms the last
time I checked, many moons ago. (I normally don't use
--enable-link-time-optimization as it makes --enable-gcc-warnings way
too slow.)
I don't think -flto per se is the issue here, though it's hard to be
sure since we weren't given a precise recipe for reproducing the bug
(and I don't use Gentoo so it'd be hard for me to reproduce it anyway).
next prev parent reply other threads:[~2024-03-10 21:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 3:19 bug#69689: 30.0.50; cannot native compile with -flto in native-comp-compiler-options StrawberryTea
2024-03-10 6:24 ` Eli Zaretskii
2024-03-10 17:32 ` StrawberryTea
2024-03-10 17:47 ` Eli Zaretskii
2024-03-10 21:08 ` Paul Eggert [this message]
2024-03-11 13:38 ` Eli Zaretskii
2024-03-12 1:03 ` Paul Eggert
2024-03-15 17:02 ` Andrea Corallo
2024-03-17 18:17 ` StrawberryTea
2024-03-17 22:09 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87zfuwy0gq.fsf@>
2024-03-17 22:12 ` StrawberryTea
2024-04-02 8:56 ` Andrea Corallo
2024-03-12 4:23 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=d6d5d7dd-0b75-4b40-8b0e-90d047f0aaae@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=69689@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=look@strawberrytea.xyz \
/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).