[PATCH] D38154: [PassManager] Run global opts after the inliner

[Sean Silva via llvm-commits]

This is super handy Matthias! Would it make sense to put this in a
docs/CTMark.rst file? I think a lot more people would be running ctmark
with a simple quickstart like this available. (And some of the tips you
mentioned downthread).

Looking at test-suite/CTMark/README.md it has some of the pieces of
information, but it doesn't bring it all together like your example and my
gut is that some of the tips you mentioned are a better fit in docs/

-- Sean Silva

On Oct 10, 2017 3:07 PM, "Matthias Braun via Phabricator via llvm-commits" <
llvm-commits at lists.llvm.org> wrote:

> MatzeB added a comment.
>
> For the record, measuring CTMark can be as easy as this without any LNT
> involved:
>
>   git clone http://llvm.org/git/test-suite.git
>   mkdir test-suite-build
>   cd test-suite-build
>   cmake -DCMAKE_C_COMPILER=/path/to/my/clang -GNinja
> -DTEST_SUITE_SUBDIRS=CTMark -DTEST_SUITE_RUN_BENCHMARKS=Off
>   ninja
>   /path/to/my/llvm/builddir/bin/llvm-lit -o result.json .
>
> Repeat for multiple compilers/patches (or with different -DCMAKE_C_FLAGS
> etc.) and in the end use compare.py to compare the results of multiple runs.
>
>
> Repository:
>   rL LLVM
>
> https://reviews.llvm.org/D38154
>
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20171011/76b41d67/attachment.html>