similar to: [LLVMdev] running of test-suite as one step

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] running of test-suite as one step"

2013 Jun 04
2
[LLVMdev] test-suite and lnt
is test-suite being run still by itself (independent of llvm)? if so, are there public build bots for this? is lnt going to replace test-suite as the normal mechanism for running test-suite? Tia. Reed
2013 Jun 05
0
[LLVMdev] test-suite and lnt
On 4 June 2013 22:08, Reed Kotler <rkotler at mips.com> wrote: > is test-suite being run still by itself (independent of llvm)? > AFAIK, yes. http://llvm.org/docs/lnt/quickstart.html if so, are there public build bots for this? > We have one: http://lab.llvm.org:8011/builders/clang-native-arm-lnt Setting it up was just copy&paste on Zorg's config (and fixing the bugs
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
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
2014 Mar 10
2
[LLVMdev] release procedure questions
On 03/10/2014 03:37 PM, Eric Christopher wrote: > cc'ing Bill as Release Manager > > On Mon, Mar 10, 2014 at 2:53 PM, reed kotler <rkotler at mips.com> wrote: >> I'm trying to understand how Mips will fit into the official release >> procedure. >> >> There are two Mips compilers: >> 1) The X86 resident llvm/clang compiler that can generate
2012 Dec 13
2
[LLVMdev] failures in test-suite for make TEST=simple
The first one failed on a diff: ******************** TEST (simple) 'sse.expandfft' FAILED! ******************** Execution Context Diff: /home/rkotler/llvmpb3/build/projects/test-suite/tools/fpcmp: Compared: 1.139094e-07 and 1.159249e-07 abs. diff = 2.015500e-09 rel.diff = 1.738626e-02 Out of tolerance: rel/abs: 1.600000e-02/0.000000e+00 ******************** TEST (simple)
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
2016 Apr 21
2
RFC: LNT/Test-suite support for custom metrics and test parameterization
On 21 Apr 2016, at 15:00, Elena Lepilkina <Elena.Lepilkina at synopsys.com<mailto:Elena.Lepilkina at synopsys.com>> wrote: Hi Kristof and Daniel, Thanks for your answers. Unfortunately I haven’t tried scaling up to a large data set before. Today I tried and results are quite bad. So database scheme should be rebuild. Now I thought about creating one sample table for each test-suite,
2013 Aug 24
1
[LLVMdev] redundant code in Mips arch?
On Sat, Aug 24, 2013 at 2:15 AM, Reed Kotler <rkotler at mips.com> wrote: > Hi Jun, > > Are you using the Mips compiler or working on it? > > yes, i am looking at its code to understand this architecture. thanks. Jun > > On 08/22/2013 11:12 PM, Jun Koi wrote: > >> hi, >> >> there are two arrays named DecoderTable32[] and DecoderTable16[] that
2012 Dec 13
1
[LLVMdev] failures in test-suite for make TEST=simple
I use the 'make TEST=simple' as a pre-commit test. I think that everybody should run these tests before committing to LLVM. On Dec 12, 2012, at 5:06 PM, reed kotler <rkotler at mips.com> wrote: > when I create the report, there are no failures in it. so maybe these are being filtered for known failures. > > On 12/12/2012 05:03 PM, reed kotler wrote: >> The first
2012 Dec 13
0
[LLVMdev] failures in test-suite for make TEST=simple
when I create the report, there are no failures in it. so maybe these are being filtered for known failures. On 12/12/2012 05:03 PM, reed kotler wrote: > The first one failed on a diff: > ******************** TEST (simple) 'sse.expandfft' FAILED! > ******************** > Execution Context Diff: > /home/rkotler/llvmpb3/build/projects/test-suite/tools/fpcmp: Compared: >
2012 Dec 15
3
[LLVMdev] test-suite
I have an approved target independent putback and i've run all that we have at Mips as well as on x86 " make TEST=simple" Is there anything else that is easy to run that I can do before doing the commit? The patch touches a number of basic classes so I'm just trying to err on the side of caution.
2013 Jan 07
0
[LLVMdev] Test Suite - Livermore Loops
On Mon, Jan 7, 2013 at 12:58 PM, Daniel Dunbar <daniel at zuster.org> wrote: > To weigh in here... > > > On Thu, Jan 3, 2013 at 8:15 AM, David Blaikie <dblaikie at gmail.com> wrote: >> >> +Daniel & Michael who work on the LNT infrastructure & might have some >> thoughts on the differences & their merits & motivations. >> >> On
2015 Jul 07
4
[LLVMdev] Recording hash of binaries in test-suite and LNT.
I've implemented a test-suite patch and an LNT patch to calculate a hash function for each binary in the test-suite & to store it in the LNT database. The test-suite patch is surprisingly simple. The only thing I had to do to get stable hashes is to strip out the .comment and all .note sections. The attached spreadsheet shows the calculated hashes by the patch across the test-suite for a
2012 Dec 15
0
[LLVMdev] test-suite
On Sat, Dec 15, 2012 at 12:33 PM, Reed Kotler <rkotler at mips.com> wrote: > I have an approved target independent putback and i've run all that we > have at Mips as well as on x86 " make TEST=simple" > > Is there anything else that is easy to run that I can do before doing the > commit? > > The patch touches a number of basic classes so I'm just
2013 Jan 08
0
[LLVMdev] Test Suite - Livermore Loops
On Tue, Jan 8, 2013 at 1:40 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 8 January 2013 04:49, Duncan Sands <baldrick at free.fr> wrote: >> >> While this should be investigated, >> I'm tempted to just move everything over to LNT instead... > > > That's the latent bugs that David mentioned. I agree we should have LNT and > LNT+LTO
2013 Jan 07
2
[LLVMdev] Test Suite - Livermore Loops
On Mon, Jan 7, 2013 at 1:14 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Mon, Jan 7, 2013 at 12:58 PM, Daniel Dunbar <daniel at zuster.org> wrote: > > To weigh in here... > > > > > > On Thu, Jan 3, 2013 at 8:15 AM, David Blaikie <dblaikie at gmail.com> > wrote: > >> > >> +Daniel & Michael who work on the LNT
2013 Mar 28
0
[LLVMdev] llvmlab (phased buildmaster) is in production mode!
Most of the selections, like "console" for example, do not work when I click on them. On 03/27/2013 03:57 PM, Michael Gottesman wrote: > Hello LLVM Dev and Clang Dev! > > David Dean and I just finished bringing up a new build master on > lab.llvm.org <http://lab.llvm.org/>, llvmlab, which is located at the > url http://lab.llvm.org:8013
2013 Jan 07
0
[LLVMdev] Test Suite - Livermore Loops
On Mon, Jan 7, 2013 at 1:46 PM, Daniel Dunbar <daniel at zuster.org> wrote: > > > > On Mon, Jan 7, 2013 at 1:14 PM, David Blaikie <dblaikie at gmail.com> wrote: >> >> On Mon, Jan 7, 2013 at 12:58 PM, Daniel Dunbar <daniel at zuster.org> wrote: >> > To weigh in here... >> > >> > >> > On Thu, Jan 3, 2013 at 8:15 AM, David
2012 Dec 13
2
[LLVMdev] failures in test-suite for make TEST=simple
I'm getting three failures. TEST-FAIL: exec /home/rkotler/llvmpb3/build/projects/test-suite/SingleSource/UnitTests/Vector/SSE/sse.expandfft TEST-RESULT-exec-time: user 0.3200 TEST-RESULT-exec-real-time: real 0.3172 TEST-FAIL: exec /home/rkotler/llvmpb3/build/projects/test-suite/SingleSource/UnitTests/Vector/SSE/sse.stepfft TEST-RESULT-exec-time: user 0.4000