-
Currently I see a build failure for LTO build. Maybe there's a problem with the arch object which is linked with the plain `ld`.
```
$ ./configure --cflags=-flto
$ make
...
LINK arch/x…
-
With:
```toml
[profile.release]
lto = true
```
in my workspace `Cargo.toml` running `cargo fuzz run «target»` fails to link with:
```
= note: rust-lld: error: undefined symbol: __sancov_ge…
-
In #5904, LTO was added to our release profile. However, in #5984, this failed for just the ppc64le musl cross build (which uses the nightly toolchain):
```
error: failed to get bitcode from obje…
-
Currently, a Cargo profile of `lto = false` is actually "thin local" LTO where LTO is performed across the local crate's codegen units. I'm wondering if that should actually be treated as `-C lto=off…
-
I am try to build livepatch for kernel built with CONFIG_LTO_CLANG.
The first issue was these .o files are not ELF files, but LLVM IR bitcode. To resolve this, I made [some hack](https://github.com/…
-
currently if you try link against a cfi-built .a you merely get
```
ld: error: inconsistent LTO Unit splitting (recompile with -fsplit-lto-unit)
```
this is because fsanitize=cfi implies -fspl…
-
From @zamazan4ik:
The `Cargo.toml` file Link-Time Optimization (LTO) for the Rust part of the project is not enabled. I suggest switching it on since it will reduce the binary size (always a good t…
-
I'm getting some confusing optimisation remarks, such as:
```
anyhow::error::::msg will not be inlined into paketkoll_core::backend::arch::mtree::extract_mtree because its definition is unavailabl…
-
```
x86_64-pc-linux-gnu-gcc -march=native -fstack-protector-all -O2 -pipe -fdiagnostics-color=always -frecord-gcc-switches -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-clash-protection -flto=4 -Wer…
-
What are the parameters recommendations for LTO cells? For example, when using LiFePO4 the parameters generated by the wizard for 4 20AH cells are the following:
```
CELLS: 4
CHG_BULK_STOP_VOLTAGE:…