This also impacts Chromium. All our executables are in all archives. E.g.
https://build.chromium.org/p/chromium.linux/builders/Linux%20Builder%20%28dbg%29/builds/104319/steps/package%20build/logs/stdio

The archive of one debug build is 7GB. I think we can chop off ~2GB from this by fixing this issue. The overall savings for upload/download/storage across the whole fleet would be ... quite large.

It also currently doesn't scale because the number of fuzzers is growing.

I also think cctest and unittests can be disregarded. The fuzzers are the main problem.

d8 is fixed now, no?

I'd expect that switching the fuzzers and unittests will be easy...

I can take a look at this.

For the record, also mksnapshot might be able to share the same library with v8_shell in the snapshot toolchain or with all the executables if snapshot toolchain == target toolchain.

Also v8_parser_shell is large.

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/22606f0c29421d6a72e46595ec2995c7771ff070

commit 22606f0c29421d6a72e46595ec2995c7771ff070
Author: jgruber <jgruber@chromium.org>
Date: Mon Sep 26 07:40:24 2016

Enable component builds for fuzzers

V8 is collecting a growing amount of fuzzers, all of which take substantial
space on the bots and in chromium build archives. This CL improves that
situation by allowing component (shared library) builds for almost all fuzzers.

The parser fuzzer is handled as an exception since it would require exporting a
large number of additional functions.

A component build results in about a 50-100x improvement in file size for each
fuzzer (~50M-100M to around 1.1M).

BUG= chromium:648864 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_compile_dbg_ng;master.tryserver.chromium.android:android_clang_dbg_recipe

Review-Url: https://codereview.chromium.org/2360983002
Cr-Commit-Position: refs/heads/master@{#39709}

[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/BUILD.gn
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/assert-scope.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/contexts.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/execution.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/factory.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/handles.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/lookup.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/machine-type.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/objects.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/regexp/jsregexp.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/wasm/ast-decoder.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/wasm/encoder.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/wasm/module-decoder.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/wasm/wasm-interpreter.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/wasm/wasm-js.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/wasm/wasm-module.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/wasm/wasm-result.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/zone/accounting-allocator.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/src/zone/zone.h
[modify] https://crrev.com/22606f0c29421d6a72e46595ec2995c7771ff070/test/fuzzer/fuzzer.gyp

After the fuzzer commit (see above), there are only a few remaining large files:

cctest
unittests
libv8.so
mksnapshot
generate-bytecode-expectations
v8_parser_shell
v8_simple_parser_fuzzer

Of these, 

* we can't do anything about libv8.so; 
* cctest, v8_parser_shell and v8_simple_parser_fuzzer use too many internal functions to make component builds practical;

That leaves unittests, mksnapshot and generate-bytecode-expectations for potential savings.

Closing this issue since the bots should now be able to handle our archive with fuzzer file size reductions. Opened issue 650171 for the remaining binaries.

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/d85a349771482333e5f9b5a0febf57f77a48ab00

commit d85a349771482333e5f9b5a0febf57f77a48ab00
Author: machenbach <machenbach@chromium.org>
Date: Mon Sep 26 10:22:11 2016

[build] Enable shared libraries for arm debug

BUG= chromium:648864 ,chromium:648610
NOTRY=true
TBR=jgruber@chromium.org

Review-Url: https://codereview.chromium.org/2371713002
Cr-Commit-Position: refs/heads/master@{#39712}

[modify] https://crrev.com/d85a349771482333e5f9b5a0febf57f77a48ab00/infra/mb/mb_config.pyl

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/f72b4a084af38e767acfe7470dbd93fb06281000

commit f72b4a084af38e767acfe7470dbd93fb06281000
Author: machenbach <machenbach@chromium.org>
Date: Tue Sep 27 09:46:20 2016

[build] Use shared libraries by default for debug builds

BUG= chromium:648864 

Review-Url: https://codereview.chromium.org/2373743002
Cr-Commit-Position: refs/heads/master@{#39754}

[modify] https://crrev.com/f72b4a084af38e767acfe7470dbd93fb06281000/infra/mb/mb_config.pyl
[modify] https://crrev.com/f72b4a084af38e767acfe7470dbd93fb06281000/src/checks.h
[modify] https://crrev.com/f72b4a084af38e767acfe7470dbd93fb06281000/src/handles.h

Thanks a lot for fixing this!

I left some comments on the CL about the impact of this across the fleet:
https://codereview.chromium.org/2360983002