summary refs log tree commit diff
path: root/Cargo.toml
diff options
context:
space:
mode:
authorZach Reizner <zachr@google.com>2019-03-01 18:14:54 -0800
committerchrome-bot <chrome-bot@chromium.org>2019-03-05 12:58:42 -0800
commit083cc4a286d740c3787117c999c935ff68ad2dc9 (patch)
treecac2845e128beff3e689def56ed9597776212513 /Cargo.toml
parentb852264e21df6066ef992168319fdae85613d22c (diff)
downloadcrosvm-083cc4a286d740c3787117c999c935ff68ad2dc9.tar
crosvm-083cc4a286d740c3787117c999c935ff68ad2dc9.tar.gz
crosvm-083cc4a286d740c3787117c999c935ff68ad2dc9.tar.bz2
crosvm-083cc4a286d740c3787117c999c935ff68ad2dc9.tar.lz
crosvm-083cc4a286d740c3787117c999c935ff68ad2dc9.tar.xz
crosvm-083cc4a286d740c3787117c999c935ff68ad2dc9.tar.zst
crosvm-083cc4a286d740c3787117c999c935ff68ad2dc9.zip
crosvm: remove LTO from release profile
Builders of crosvm, such as the crosvm ebuild, should determine if they
want LTO enabled. By having lto removed from the release profile,
builders using `--release` will not be forced to use LTO.

BUG=None
TEST=cargo build --release should be heckin' fast

Change-Id: I4e231b6dac7670ab146d36c1c1660ab67935285a
Reviewed-on: https://chromium-review.googlesource.com/1497734
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: kokoro <noreply+kokoro@google.com>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Diffstat (limited to 'Cargo.toml')
-rw-r--r--Cargo.toml1
1 files changed, 0 insertions, 1 deletions
diff --git a/Cargo.toml b/Cargo.toml
index dd0be66..cc39e5b 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -4,7 +4,6 @@ version = "0.1.0"
 authors = ["The Chromium OS Authors"]
 
 [profile.release]
-lto = true
 panic = 'abort'
 overflow-checks = true