Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How to turn off LTO (link-time optimization)?

  • ما من ردود
  • 0 have this problem
  • 11 views
more options

i'm trying to help NetBSD by maintaining rust for a number of NetBSD targets. As part of that, I use rust and verify that its "major packages" still build, firefox among them. Recently I found (ref. https://github.com/rust-lang/rust/issues/143904) that by default, firefox would no longer build natively on NetBSD/i386 (really i586 / i686, in 32-bit mode). I found a workaround, namely to turn off address-space layout randomization, but this indicates we are already balancing too close to the border of the 3GB per-process data segment size for comfort. A hint given there was that I could try to turn off LTO (link-time optimization), since it reportedly gives at best modest gains for considerable cost in terms of build time and VM space requirements during the build.

So... This is my first encounter with the firefox configure machinery which is different from most other similar things, and I appear to be unable to find a way to instruct the configure machinery to build without LTO. The configure script accepts `--disable-lto` (no, that is not present in the `--help` output), but evidently this option does not do what it implies: I still see rustc threads during the build which set their name to a string containing "lto".

So... "Help!"

i'm trying to help NetBSD by maintaining rust for a number of NetBSD targets. As part of that, I use rust and verify that its "major packages" still build, firefox among them. Recently I found (ref. https://github.com/rust-lang/rust/issues/143904) that by default, firefox would no longer build natively on NetBSD/i386 (really i586 / i686, in 32-bit mode). I found a workaround, namely to turn off address-space layout randomization, but this indicates we are already balancing too close to the border of the 3GB per-process data segment size for comfort. A hint given there was that I could try to turn off LTO (link-time optimization), since it reportedly gives at best modest gains for considerable cost in terms of build time and VM space requirements during the build. So... This is my first encounter with the firefox configure machinery which is different from most other similar things, and I appear to be unable to find a way to instruct the configure machinery to build without LTO. The configure script accepts `--disable-lto` (no, that is not present in the `--help` output), but evidently this option does not do what it implies: I still see rustc threads during the build which set their name to a string containing "lto". So... "Help!"

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.