similar to: [LLVMdev] git repository for test suite?

I run the test suite by CD-ing into /projects/test-suite and running "make TEST=simple -j 4". On Dec 12, 2012, at 10:13 AM, Reed Kotler <rkotler at mips.com> wrote: > I'm trying to run test-suite for x86 in order to verify a target independent patch before I put it back. > The patch has been approved. > > What is the best way to run it in order to get maximum

I'm trying to run test-suite for x86 in order to verify a target independent patch before I put it back. The patch has been approved. What is the best way to run it in order to get maximum coverage and have results where I can tell that I have not regressed anything (as well as the test-suite can help with that)? I've already tested it against the Mips compiler but we have a slightly

On 12/12/2012 10:18 AM, Nadav Rotem wrote: > I run the test suite by CD-ing into /projects/test-suite and running "make TEST=simple -j 4". > > > On Dec 12, 2012, at 10:13 AM, Reed Kotler <rkotler at mips.com> wrote: > >> I'm trying to run test-suite for x86 in order to verify a target independent patch before I put it back. >> The patch has been

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

On 11/07/2011 02:29 PM, Eli Friedman wrote: > On Mon, Nov 7, 2011 at 2:11 PM, reed kotler<rkotler at mips.com> wrote: >> We have a modified version of projects/test-suite that we can run cross >> using Qemu. >> >> We would like to put that back so that other people can test MIPS >> before putting back. >> Well, this would be easily modifiable for ARM

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

On Mon, Nov 7, 2011 at 2:11 PM, reed kotler <rkotler at mips.com> wrote: > We have a modified version of projects/test-suite that we can run cross > using Qemu. > > We would like to put that back so that other people can test MIPS > before putting back. > Well, this would be easily modifiable for ARM and other targets that are > supported by QEMU. > > But in this

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: >

Yes, it looks like the core is all GPL2. But they go on a file-by-file basis. Chris Matthews chris.matthews at apple.com (408) 783-6335 On Jul 11, 2013, at 5:29 PM, Reed Kotler <rkotler at mips.com> wrote: > Be careful about license issues. > > I.e. gpl. > > > On 07/11/2013 05:00 PM, Chris Matthews wrote: >> I am looking at adding some tests based on John the

On 12/15/2012 12:53 PM, Chandler Carruth wrote: > On Sat, Dec 15, 2012 at 12:33 PM, Reed Kotler <rkotler at mips.com > <mailto: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

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)

We have a modified version of projects/test-suite that we can run cross using Qemu. We would like to put that back so that other people can test MIPS before putting back. Well, this would be easily modifiable for ARM and other targets that are supported by QEMU. But in this case, we would need to check in a version of QEMU and also the needed pieces of a MIPS tool chain for assembly,

Currently, if you are on Mips hardware running linux, you can basically just run test suite the same way you would run it on an x86 box. You can just do a "make report TEST=simple" for example. We also run it on an x86 box, generating MIPS code and then use either qemu as a simulator or connect to a mips linux box to just execute the tests. To do this cross compilation and testing,

I forgot to mention that you can also run "make TEST=simple report" which will generate a nice report. Do you know why these tests fail ? You can step into the test directory and run 'make TEST=simple' from there. It will save you some time. On Dec 12, 2012, at 4:04 PM, reed kotler <rkotler at mips.com> wrote: > I'm getting three failures. > > TEST-FAIL:

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

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

I have some test scripts I use for testing floating point interoperability between mips16 and mips32. There are lots of combinations and there are subtle issues that make them slightly different and they need to all be tested. For a very basic test, I have a program which has a sample function of all floating point signatures that are effected by this. Basically an ABI test for this. This

On 12/15/2012 12:53 PM, Chandler Carruth wrote: > On Sat, Dec 15, 2012 at 12:33 PM, Reed Kotler <rkotler at mips.com > <mailto: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

`llvm-lit path/to/test/file/here` Joey On 12 January 2013 12:08, Reed Kotler <rkotler at mips.com> wrote: > Is there a way to just run one test with "make check" for either the llvm > or clang test suites? > > Tia. > > Reed > ______________________________**_________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu

On Feb 17, 2013, at 1:01 PM, Reed Kotler <rkotler at mips.com> wrote: > On 02/17/2013 12:48 PM, Andrew Trick wrote: >> On Feb 16, 2013, at 1:31 PM, Cameron Zwarich <zwarich at apple.com> wrote: >> >>> That's exactly the right place. >> Really? You don't want the expansion to be optimized? You want to specify a machine model for the pseudo's