Displaying 3 results from an estimated 3 matches for "as_clang".
Did you mean:
dis_clang
2015 Apr 01
4
[LLVMdev] [RFC] Setting preserve-bc-use-list-order=true by default
...n clang with running time >= 1 second (details in
dis_clang.txt, attached).
- Time increase of running `llvm-as` on merged bitcode files:
— 3.5% to 39% on SPEC benchmarks with running time >= 1 second.
— 14.7% to 24.5% with running time >= 1 second (details in
as_clang.txt, attached).
Does it work?
=============
Manman also ran `verify-uselistorder` (a use-list fuzzer that shuffles
use-lists, serializes IR, compares use-lists, rinses, repeats), on the
merged bitcode files above. After I fixed a bug in assembly
serialization in r232200, they all come up clean....
2015 Apr 09
3
[LLVMdev] [RFC] Setting preserve-bc-use-list-order=true by default
...>= 1 second (details in
> dis_clang.txt, attached).
> - Time increase of running `llvm-as` on merged bitcode files:
> — 3.5% to 39% on SPEC benchmarks with running time >= 1 second.
> — 14.7% to 24.5% with running time >= 1 second (details in
> as_clang.txt, attached).
>
> These seem like pretty big costs to pay (bitcode size is going to be particularly important to Google - big projects under LTO, limits on the total size of the inputs to the link step, etc). To the point above, it's not clear why we'd want to pay that cost. (I'...
2015 Apr 14
2
[LLVMdev] [RFC] Setting preserve-bc-use-list-order=true by default
...in
> > dis_clang.txt, attached).
> > - Time increase of running `llvm-as` on merged bitcode files:
> > — 3.5% to 39% on SPEC benchmarks with running time >= 1 second.
> > — 14.7% to 24.5% with running time >= 1 second (details in
> > as_clang.txt, attached).
> >
> > These seem like pretty big costs to pay (bitcode size is going to be particularly important to Google - big projects under LTO, limits on the total size of the inputs to the link step, etc). To the point above, it's not clear why we'd want to pay that cos...