Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] LLVM lnt - Test Backend Pass"
2013 Mar 11
2
[LLVMdev] LNT usage
While porting my backends to llvm-3.2, I found a few places where the
optimizers could have performed better. I believe the mainstream targets can
also benefits from my tweaks. But before upstreaming my changes, I would like
to quantify their merits on other applications --- not just my domain specific
codes. In a word, it seemed the right time for me to start using LNT :)
I followed the
2014 Mar 14
2
[LLVMdev] clang/lnt buildbot on F20 "lnt: error: no such option: -m" ...
Hi
Since the buildbot host was updated to Fedora F20 levels, the clang
buildbot has been failing with the following:
$ /home/clangbuild/clang-ppc64-1/lnt.venv/bin/lnt runtest --verbose --submit http://llvm.org/perf/submitRun --commit=1 nt --sandbox nt --no-timestamp --cc /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang --cxx /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang++
2013 Jun 10
1
[LLVMdev] Cannot submit LLVM test-suite results to the database using LNT tool
Hello,
When I was running the LNT testing for LLVM test-suite, it failed to submit the results to database.
The command is:
lnt runtest --submit db nt
--sandbox sandbox --cc clang --cxx clang++ --test-suite ./test-suite-3.2/ --llvm-src ~/projects/llvm/llvm --llvm-obj ~/projects/llvm/llvm_build/ --test-style=nightly --only-test MultiSource/Benchmarks/mediabench/
When submitting the results
2012 Sep 18
0
[LLVMdev] Cannot import LLVM test-suite results to the database using LNT tool
Hi,
I follow quick-start guide http://llvm.org/docs/lnt/quickstart.html to
run LLVM test-suite. It looks like I either make a mistake or the
guide is not correct.
Here is the command used to run nightly test:
[[
$ lnt runtest nt --sandbox=$PWD/test-suite.bld \
--small --test-style=nightly \
--cc=$PWD/llvm.bld/Release+Asserts/bin/clang \
--cxx=$PWD/llvm.bld/Release+Asserts/bin/clang++
2015 Jan 29
2
[LLVMdev] LNT install
I followed the lnt quickstart <http://llvm.org/docs/lnt/quickstart.html> directions but got this diagnostic when doing the setup:
bash-3.2$ ~/mysandbox/bin/python ~/lnt/setup.py develop
/Users/dcallahan/mysandbox/lib/python2.7/site-packages/setuptools/dist.py:284: UserWarning: The version spec\
ified requires normalization, consider using '0.4.1.dev0' instead of
2012 Apr 12
2
[LLVMdev] Running test suite with LNT failed
Hi all,
I am running LNT with LLVM/Clang 3.0 Release binary and test suite, here is my
flow (most of them are the same as http://llvm.org/docs/lnt/quickstart.html).
---
$ svn co http://llvm.org/svn/llvm-project/lnt/trunk ~/lnt
$ ~/mysandbox/bin/python ~/lnt/setup.py develop
$ cd mysandbox; source bin/activate
$ $ lnt runtest nt \
--sandbox SANDBOX \
--cc
2015 Jan 30
1
[LLVMdev] LNT install
Hi David,
That's weird, I have setup LNT in multiple different distros and have
never seen this. Looks like no one ever tested on the system you're
running. Can you share a bit more of your environment?
Also, you can check the setup.py to see if it does any stripping of
package names, which could go wrong in the wrong environment.
cheers,
--renato
On 29 January 2015 at 20:13, David
2012 Jun 13
0
[LLVMdev] LNT always using clang++ as linker command
Hi,
I'm using LNT to run the llvm nightly tests. When it's compiling the
tests, it seems to always use the clang++ driver as the linker command
instead of clang, even for tests that are pure C code. This makes all
the binaries depend on libstdc++, which isn't great.
This happens even if I specify --disable-cxx. The only way around it
seems to be to also specify clang as the C++
2012 Apr 13
0
[LLVMdev] Running test suite with LNT failed
On Wed, Apr 11, 2012 at 7:59 PM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote:
> Hi all,
>
> I am running LNT with LLVM/Clang 3.0 Release binary and test suite, here is my
> flow (most of them are the same as http://llvm.org/docs/lnt/quickstart.html).
>
> ---
> $ svn co http://llvm.org/svn/llvm-project/lnt/trunk ~/lnt
> $ ~/mysandbox/bin/python ~/lnt/setup.py develop
>
2016 Apr 22
2
RFC: LNT/Test-suite support for custom metrics and test parameterization
On 21 Apr 2016, at 17:44, Sergey Yakoushkin <sergey.yakoushkin at gmail.com<mailto:sergey.yakoushkin at gmail.com>> wrote:
Hi Kristof,
The way we use LNT, we would run different configuration (e.g. -O3 vs -Os) as different "machines" in LNT's model.
O2/O3 is indeed bad example. We're also using different machines for Os/O3 - such parameters apply to all
2013 Jun 07
0
[LLVMdev] tools build issue with lnt in cross platform testing
The issues seems to be this line in the tools Makefile
timeit-target: timeit.c
$(LD_ENV_OVERRIDES) $(LCC) -o $@ $< $(LDFLAGS) $(CFLAGS)
$(TARGET_FLAGS) -O3
It should not add target flags if we are simulating the target on the host.
On 06/06/2013 06:59 PM, reed kotler wrote:
> I want to get lnt to use qemu for the execution.
>
> In that case, RHOST= is not set.
>
> But I
2013 Jun 07
2
[LLVMdev] tools build issue with lnt in cross platform testing
I want to get lnt to use qemu for the execution.
In that case, RHOST= is not set.
But I change the Arch because I am going to run in cross mode.
Then I'm setting RUNUNDER to be a script which runs qemu.
In this case it builds timeit-target as a Mips which fails because this
is running on x86.
~/mysandbox/bin/lnt runtest nt --sandbox ~/mysandbox --cc
/local/llvmpb_a/install/bin/clang
2018 Jun 05
2
How to get optimization remarks while testing with lnt in llvm
Hi, I'm new to llvm and am trying to run benchmarks from the test-suite
using lnt to check loop-vectorization for various benchmarks.
Test are compiling and executing fine, but I am not getting optimization
remarks while using flags like -Rpass-missed=loop-vectorize and
-Rpass-analysis=loop-vectorize
I've tried running it like this:
lnt runtest test-suite --sandbox SANDBOX --cc
2013 Mar 11
0
[LLVMdev] LNT usage
> 2. Running lnt several times on the same unmodified clang+llvm binaries gives
> different results (execution time can vary wildly : ~200%). I am running lnt
> on linux/x86_64. I tried to deactivate the cpufreq thing, the machine was not
> loaded, but this did not change. Is there any way to run the tests multiple
> times and use statistics to get reproducible numbers (within a
2012 Sep 06
0
[LLVMdev] LNT: failing to parse compiler info: what am I doing wrong?
On Wed, Sep 5, 2012 at 7:23 PM, Sean Silva <silvas at purdue.edu> wrote:
> Hi, I'm trying to use LNT to run the test-suite. I followed the
> instructions on <http://lnt.llvm.org/quickstart.html>. When I run it I
> get this error:
>
> (mysandbox)sean:~/pg/others/llvm % lnt runtest nt --sandbox mysandbox
> --cc ~/pg/others/llvm/release/bin/clang --test-suite
2016 Apr 22
2
RFC: LNT/Test-suite support for custom metrics and test parameterization
On 22 Apr 2016, at 11:14, Mehdi Amini <mehdi.amini at apple.com<mailto:mehdi.amini at apple.com>> wrote:
On Apr 22, 2016, at 12:45 AM, Kristof Beyls via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
On 21 Apr 2016, at 17:44, Sergey Yakoushkin <sergey.yakoushkin at gmail.com<mailto:sergey.yakoushkin at gmail.com>> wrote:
Hi
2012 Sep 06
2
[LLVMdev] LNT: failing to parse compiler info: what am I doing wrong?
Hi, I'm trying to use LNT to run the test-suite. I followed the
instructions on <http://lnt.llvm.org/quickstart.html>. When I run it I
get this error:
(mysandbox)sean:~/pg/others/llvm % lnt runtest nt --sandbox mysandbox
--cc ~/pg/others/llvm/release/bin/clang --test-suite test-suite
nt.py:1185: note: inferred C++ compiler under test as:
2012 Sep 06
1
[LLVMdev] LNT: failing to parse compiler info: what am I doing wrong?
> And it doesn't match probably because of one of two things (& I forget
> which of the two, if either, have been addressed/workaround):
>
> 1) using cmake instead of configure/make
> 2) using git instead of svn
>
> One or both of these create versions that lnt doesn't understand
> (because they don't include the SVN revision number in the clang
> version
2019 Aug 08
2
LNT server function perf profile comparison
Hi!
I have implemented a security feature in LLVM and now I want to evaluate the performance impact by comparing the perf profile of the originally compiled program and the modified program. For that I have run a benchmark with lnt runtest test-suite and -use-perf=all. I can compare the recorded counters in the lnt runserver webinterface perfectly fine with the side by side comparison. However,
2017 Feb 28
2
Noisy benchmark results?
> On Feb 27, 2017, at 1:36 AM, Kristof Beyls via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hi Mikael,
>
> Some noisiness in benchmark results is expected, but the numbers you see seem to be higher than I'd expect.
> A number of tricks people use to get lower noise results are (with the lnt runtest nt command line options to enable it between brackets):
> *