Shane Peelar

Sure, but you might consider cross compiling instead of building on the RPi itself. You can use `distcc` to do that fairly easily.

If your concern is the other features `app-portage/portage-bashrc-mv` provides, you can disable `USE=ccache remove-la title` on it which should do just that. Indeed, `sys-config/ltoize` only depends on the `cflags` USE...

Anyone willing to do a PR? I don't use Chromium myself and I remember it took forever to compile.

I just look at the build logs, however if there are any static libraries, you can `objdump` them to see if there are any GIMPLE symbols in the output. Example...

@Hello71, were you able to just use `custom-cflags` or did it require more in-depth workarounds?

Does `lto-rebuild -l` work?

Leave the `source` lines out of your `make.conf`, and make sure your `CFLAGS` are set to default. If you want to be ultra safe, remove `portage-bashrc-mv`. If you're still experiencing...

Now that I think about it, we can handle Fortran right now. I'm pretty sure we can set `FFLAGS` and `FCFLAGS` to `CFLAGS` without any issue and gain LTO that...

Additional reading: https://github.com/rust-lang/rust/issues/48518 Interestingly, ThinLTO leaves out certain optimizations that monolithic LTO enables. I'm experimenting with monolithic LTO currently.

To anyone wanting to try out rust LTO. For ThinLTO: ~~~ RUSTFLAGS="-C codegen-units=${NTHREADS} -Z thinlto" ~~~ For monolithic LTO: ~~~ RUSTFLAGS="-C lto=fat -C codegen-units=1" ~~~