build: LTO profile 'thin' and moved to Cargo.toml
It makes more sense to set the release LTO profile into the related Cargo.toml section than into the Dockerfile only.
Using LTO 'thin' profile because according to the documentation it is a good compromise with no or little performance loss.
Merge request reports
Activity
Filter activity
added RN-silent label
added 2 commits
requested review from @HugoTrentesaux
added 1 commit
- cf4ed969 - build: LTO profile 'thin' and moved to Cargo.toml
added 3 commits
-
cf4ed969...10170f2a - 2 commits from branch
master
- 59111f8f - build: LTO profile 'thin' and moved to Cargo.toml
-
cf4ed969...10170f2a - 2 commits from branch
enabled an automatic merge when the pipeline for 59111f8f succeeds
Please register or sign in to reply