From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69689@debbugs.gnu.org, look@strawberrytea.xyz
Subject: bug#69689: 30.0.50; cannot native compile with -flto in native-comp-compiler-options
Date: Mon, 11 Mar 2024 18:03:32 -0700 [thread overview]
Message-ID: <bd3d76cd-b3d5-4035-96aa-6e5484ac0e7c@cs.ucla.edu> (raw)
In-Reply-To: <865xxsvqg4.fsf@gnu.org>
On 3/11/24 06:38, Eli Zaretskii wrote:
> configure.ac says "experimental", so I guess it's not yet reliable
> enough?
It was added by Dmitry Antipov in 2012. I never use it, and didn't even
recall it until I looked at configure.ac recently.
I've not have good luck with -lto elsewhere. It can make linking slow
and it tends to expose compiler bugs. Unless someone's using it
regularly I would consider it experimental.
> It also uses the getconf command (to figure out the number of CPU
> cores?), which AFAIK is for glibc-only systems, right?
Yes, but if getconf is missing 'configure' is supposed to do something
reasonable anyway.
next prev parent reply other threads:[~2024-03-12 1:03 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
2024-03-11 13:38 ` Eli Zaretskii
2024-03-12 1:03 ` Paul Eggert [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd3d76cd-b3d5-4035-96aa-6e5484ac0e7c@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 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.