Displaying 3 results from an estimated 3 matches for "1018m".
Did you mean:
1018
2018 Apr 27
3
Size of produced binaries when compiling llvm & clang sources
...any entry in the doc
that helps me understand how to reduce the size of the binaries produced.
Is this normal ? Does any one has some hint to prevent this ?
Here are the sizes of the binaries:
1.9G clang-7
1.6G clang-check
1.2G clang-tidy
1.1G opt
1.1G bugpoint
1.1G llvm-lto
1.1G llvm-lto2
1018M llc
1015M c-index-test
992M dsymutil
992M llvm-isel-fuzzer
989M llvm-opt-fuzzer
987M llvm-dwp
937M llvm-c-test
653M clang-import-test
512M clangd
493M arcmt-test
484M lli
480M clang-query
473M clang-refactor
469M clang-move
468M global-symbol-builder
467M clang-change-namespace
464M...
2018 Apr 27
0
Size of produced binaries when compiling llvm & clang sources
...e size of the binaries produced.
>
> Is this normal ? Does any one has some hint to prevent this ?
>
> Here are the sizes of the binaries:
>
> 1.9G clang-7
> 1.6G clang-check
> 1.2G clang-tidy
> 1.1G opt
> 1.1G bugpoint
> 1.1G llvm-lto
> 1.1G llvm-lto2
> 1018M llc
> 1015M c-index-test
> 992M dsymutil
> 992M llvm-isel-fuzzer
> 989M llvm-opt-fuzzer
> 987M llvm-dwp
> 937M llvm-c-test
> 653M clang-import-test
> 512M clangd
> 493M arcmt-test
> 484M lli
> 480M clang-query
> 473M clang-refactor
> 469M clang-mov...
2012 Jan 15
0
[CENTOS6] mtrr_cleanup: can not find optimal value - during server startup
...an_size: 8M chunk_size: 256M num_reg: 10 lose cover RAM: 6M
*BAD*gran_size: 8M chunk_size: 512M num_reg: 10 lose cover
RAM: -250M
gran_size: 8M chunk_size: 1G num_reg: 10 lose cover RAM: 6M
*BAD*gran_size: 8M chunk_size: 2G num_reg: 10 lose cover
RAM: -1018M
gran_size: 16M chunk_size: 16M num_reg: 10 lose cover
RAM: 70M
gran_size: 16M chunk_size: 32M num_reg: 10 lose cover
RAM: 22M
gran_size: 16M chunk_size: 64M num_reg: 10 lose cover
RAM: 22M
gran_size: 16M chunk_size: 128M...