[PATCH] IndVarSimplify : do not recompute an IV value used outside of the loop if it is trivially known not to be beneficial

Andrew Trick atrick at apple.com
Tue Mar 5 10:14:37 PST 2013


On Mar 5, 2013, at 7:30 AM, "Arnaud A. de Grandmaison" <arnaud.adegm at gmail.com> wrote:
>> 
>> I would at least gather optimization stats across llvm test-suite before supressing exit value replacement to make sure we're not preventing other optimization.
> I have never done that before, but that's a good time to start :)

There should be a way to gather stats with lnt, but I don't know how. Unfortunately, I still use the TEST=nightly like this:

make build -j8 TEST=nightly \
TARGET_FLAGS="-arch x86_64 -Wno-error=implicit-function-declaration" \
OPTFLAGS=-O3 ARCH=x86_64 CC_UNDER_TEST_TARGET_IS_X86_64=1 \
ENABLE_BUILT_CLANG=1 LLVMCC_OPTION=clang CC_UNDER_TEST_IS_CLANG=1

And the attached python script to compare runs.

-Andy

-------------- next part --------------
A non-text attachment was scrubbed...
Name: comparestats.py
Type: text/x-python-script
Size: 3339 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130305/1e316e96/attachment.bin>


More information about the llvm-commits mailing list