similar to: [LLVMdev] Disabling certain backends in test-suite?

Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] Disabling certain backends in test-suite?"

2010 Jul 10
0
[LLVMdev] Disabling certain backends in test-suite?
If you disable them at configure time, they won't be run. You probably want: --enable-targets=host --disable-jit Reid On Sat, Jul 10, 2010 at 8:56 PM, Patrick Simmons <simmon12 at illinois.edu> wrote: > Hello, > > I'm trying to add some tests from PARSEC to MultiSource, and I can't > figure out how to disable the lli and cbe backends.  Because the code > uses
2010 Jul 22
0
[LLVMdev] I would like to merge PARSEC into test-suite
It's not *that* big. The patch is 634K uncompressed. I'd say it would be annoying to have that attached to an email message, but it's no bigger than existing MultiSource tests. --Patrick On 07/21/2010 08:13 PM, Daniel Dunbar wrote: > On Wed, Jul 21, 2010 at 11:57 AM, John Criswell<criswell at uiuc.edu> wrote: > >> Daniel Dunbar wrote: >>
2010 Jul 22
2
[LLVMdev] I would like to merge PARSEC into test-suite
On Wed, Jul 21, 2010 at 11:57 AM, John Criswell <criswell at uiuc.edu> wrote: > Daniel Dunbar wrote: >> >> On Tue, Jul 20, 2010 at 1:30 AM, Owen Anderson <resistor at mac.com> wrote: >> >>> >>> Patrick, >>> >>> On Jul 20, 2010, at 1:18 AM, Patrick Simmons wrote: >>> >>>> >>>> It is open-source and
2010 Aug 05
2
[LLVMdev] PARSEC Patch
I have completed work merging PARSEC into the LLVM test suite infrastructure? The patch is available at [http://zion.cs.uiuc.edu/~simmon12/parsec.patch]. If there are no objections, would someone please commit this patch to test-suite? Best regards, --Patrick
2010 Jul 20
3
[LLVMdev] I would like to merge PARSEC into test-suite
On Tue, Jul 20, 2010 at 1:30 AM, Owen Anderson <resistor at mac.com> wrote: > Patrick, > > On Jul 20, 2010, at 1:18 AM, Patrick Simmons wrote: >> It is open-source and redistributable, and I have added LICENSE.TXT >> files to all the pieces I want to merge.  These are blackscholes, >> canneal, dedup, fluidanimate, freqmine, streamcluster, and swaptions.  I >>
2010 Jul 21
0
[LLVMdev] I would like to merge PARSEC into test-suite
Daniel Dunbar wrote: > On Tue, Jul 20, 2010 at 1:30 AM, Owen Anderson <resistor at mac.com> wrote: > >> Patrick, >> >> On Jul 20, 2010, at 1:18 AM, Patrick Simmons wrote: >> >>> It is open-source and redistributable, and I have added LICENSE.TXT >>> files to all the pieces I want to merge. These are blackscholes, >>> canneal,
2010 Aug 14
0
[LLVMdev] PARSEC Patch
Would someone please merge this for me? --Patrick On 08/05/10 13:43, Patrick Alexander Simmons wrote: > I have completed work merging PARSEC into the LLVM test suite > infrastructure? The patch is available at > [http://zion.cs.uiuc.edu/~simmon12/parsec.patch]. If there are no > objections, would someone please commit this patch to test-suite? > > Best regards, > --Patrick
2011 Nov 02
2
[LLVMdev] test suite and int main
On Wed, 2011-11-02 at 11:07 -0700, Eli Friedman wrote: > On Wed, Nov 2, 2011 at 10:38 AM, Hal Finkel <hfinkel at anl.gov> wrote: > > I'm just setting up the test suite, and I'm seeing a lot of failures > > from main() not returning int, etc. in some of the tests. Is this > > normal? > > > > For example: > >
2010 Jul 20
0
[LLVMdev] I would like to merge PARSEC into test-suite
Patrick, On Jul 20, 2010, at 1:18 AM, Patrick Simmons wrote: > It is open-source and redistributable, and I have added LICENSE.TXT > files to all the pieces I want to merge. These are blackscholes, > canneal, dedup, fluidanimate, freqmine, streamcluster, and swaptions. I > will disable the tests by default on the initial merge and test > thoroughly on Linux and MacOS before
2010 Jul 20
2
[LLVMdev] I would like to merge PARSEC into test-suite
From here: http://parsec.cs.princeton.edu It is open-source and redistributable, and I have added LICENSE.TXT files to all the pieces I want to merge. These are blackscholes, canneal, dedup, fluidanimate, freqmine, streamcluster, and swaptions. I will disable the tests by default on the initial merge and test thoroughly on Linux and MacOS before enabling them. May I please commit my
2011 Nov 02
0
[LLVMdev] test suite and int main
On Nov 2, 2011, at 11:18 AM, Hal Finkel wrote: > On Wed, 2011-11-02 at 11:07 -0700, Eli Friedman wrote: >> On Wed, Nov 2, 2011 at 10:38 AM, Hal Finkel <hfinkel at anl.gov> wrote: >>> I'm just setting up the test suite, and I'm seeing a lot of failures >>> from main() not returning int, etc. in some of the tests. Is this >>> normal? >>>
2011 Aug 04
1
[LLVMdev] Merging PARSEC into the test suite
There was some talk a year ago about a patch that merges PARSEC into the test suite. Here is a link to the thread: http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-August/033877.html Has this just fallen through the cracks? Any help on this subject is welcome. Thanks! -- Wonsun -------------- next part -------------- An HTML attachment was scrubbed... URL:
2009 Feb 07
3
[LLVMdev] Problem Running llvm-suite
Hi, I'm trying to run the tests in llvm-suite, but I've run into trouble. First, I had the llvm-suite checkout in a directory alongside the llvm compiler checkout, but, when I ran "make" from llvm-suite, it complained about there not being a Makefile two levels above it, so I moved llvm-suite into the "test" subdirectory inside the llvm compiler checkout. I ran
2010 Mar 01
1
[LLVMdev] LLVM and Pool Allocation with PARSEC?
Has anyone ever used pool allocation on PARSEC? If not, has anyone ever compiled PARSEC to whole-program LLVM bytecode executables? If you have done either of these things, would you please email me your .bldconf files? Thanks, --Patrick
2010 Jul 26
1
[LLVMdev] Marking a test suite test XFAIL
I'm sorry; I should have been more clear. I mean, for instance, run a test but only with, say, llc, not with lli or cbackend. Thanks, --Patrick Dale Johannesen wrote: > > On Jul 25, 2010, at 2:37 AMPDT, Patrick Simmons wrote: > >> Thanks, Dale, that really helps. >> >> What about disabling only one backend of a specific test? >> >> Thanks, >>
2006 Sep 03
0
[LLVMdev] Testing a register allocator
> BTW, how can I run all tests only on LLC to reduce the amount of time to > wait until tests are finished, if it's possible? In my previous reply to your question, I suggested you look at TEST.llc.Makefile and TEST.llc.report in the test directory. Modifying those makefile/report files to use your register allocator will do what you want. -Tanya
2006 Nov 14
5
[LLVMdev] 1.9 Prerelease Available for Testing
LLVMers, The LLVM 1.9 Prerelease is available for testing: http://llvm.org/prereleases/1.9/ If anyone can spare some time, please download the appropriate tarballs for your platform and test the release (at least with make check). I'd also appreciate any documentation reviews. Please note that llvm-gcc3 on x86 may not have a clean dejagnu run. You should see one XPASS for
2006 Nov 17
2
[LLVMdev] 1.9 Prerelease Available for Testing (TAKE TWO)
Hi Tanya, Here's my second attempt on Fedora Core 5. The changes this time are: 1. Using GCC 4.0.3 as the compiler 2. Building everything from source (no pre-built binaries used) BUILD LLVM WITH GCC 4.0.3 * No issues, just the usual warnings. BUILD LLVM-GCC WITH GCC 4.0.3 * No issues RUN LLVM-TEST WITH GCC 4.0.3 * The following failures were encountered. Some of them are
2006 Nov 16
0
[LLVMdev] 1.9 Prerelease Available for Testing
Tanya, Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5) HIGH LEVEL COMMENTS * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't that be llvm-1.9? * LLVM was built in Release mode in all cases * I don't think this is ready for release. In particular the llvm-gcc4 binary seg faults on FC 5 for most of llvm-test programs. *
2006 Nov 08
6
[LLVMdev] 1.9 Next Steps
I created the 1.9 release branch last night. As a reminder, please do not check in any code changes to the release branch. Please send me email if you have changes that need to be merged into the release branch. To check out the release branch: cvs -d <CVS Repository> co -r release_19 llvm cvs -d <CVS Repository> co -r release_19 llvm-test cvs -d <CVS Repository> co -r