similar to: [LLVMdev] status of EH tests in llvm test-suite

On Jan 22, 2010, at 3:01 PMPST, Jose Rangel wrote: > 2) The following test is commented out on purpose: > MultiSource/Benchmarks/Misc-C++-EH/spirit > > Should this test still be commented out? It’s actually has the most > lines of code of all your tests and seems quite useful. In addition, > it seems to work for us. Is there something wrong with this test > (e.g. buggy

hi, when i change the OBJ_ROOT and recompile the llvm, it's successful. but run following test, then the error occues: ----------------------------------------------------- [yue at RH9 obj]$ make -C ./test/Programs make: Entering directory `/home/yue/llvm/obj/test/Programs' make[1]: Entering directory `/home/yue/llvm/obj/test/Programs/SingleSource' make[2]: Entering directory

Hi Dale, Thanks for replying. Concerning Darwin, I compiled this test on snow leopard and ran it using rosetta (that is, using -arch ppc -m32). I will try this later on leopard. Thanks, Jose ________________________________ From: Dale Johannesen [mailto:dalej at apple.com] Sent: Friday, January 22, 2010 3:10 PM To: Jose Rangel Cc: Dale Johannesen; llvmdev at cs.uiuc.edu

hi, when I run "make -C ./llvm/test/Programs", it show following error: ------------------------------------------------------------------------------------------- [root at RH9 llvm]# make -C ./llvm/test/Programs make: Entering directory `/usr/local/llvm/llvm/test/Programs' make[1]: Entering directory `/usr/local/llvm/llvm/test/Programs/SingleSource' make[2]: Entering directory

At the LLVM Developers' Meeting in November, I promised to work on isolating a subset of the current test suite that is useful for benchmarking. Having looked at this in more detail, most of the applications and benchmarks in the test suite are useful for benchmarking, and so I think that a better way of phrasing it is that we should construct a list of programs in the test suite that are not

All, Just an FYI .. In order to make joint development easier and to allow LLVM developers to preview upcoming changes, I've created a new branch in LLVM CVS. Its tag name is "SignlessTypes". We will work on this branch and merge when we get stable (i.e. doesn't break anything) increments. If you're interested in what's going on, please watch the commits list for this

Target: FreeBSD 6.2-STABLE on i386 autoconf says: configure:2122: checking build system type configure:2140: result: i386-unknown-freebsd6.2 [...] configure:2721: gcc -v >&5 Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.4.6 [FreeBSD] 20060305 [...] objdir != srcdir, for both llvm and gcc. Release build. llvm-gcc 4.2 from source.

Hi, LLVM 2.1-pre1 test results: Linux (SUSE) on x86 (P4) Release mode, but with assertions enabled LLVM srcdir == objdir # of expected passes 2250 # of expected failures 5 I ran the llvm-test suite on my desktop while I was also working on that PC, so don't put too much trust in the timing info. Especially during the "spiff" test the machine was swapping

On Fri, Sep 14, 2007 at 11:42:18PM -0700, Tanya Lattner wrote: > The 2.1 pre-release (version 1) is available for testing: > http://llvm.org/prereleases/2.1/version1/ > > [...] > > 2) Download llvm-2.1, llvm-test-2.1, and the llvm-gcc4.0 source. > Compile everything. Run "make check" and the full llvm-test suite > (make TEST=nightly report). > > Send

Target: FreeBSD 7.0-RC1 on amd64. autoconf says: configure:2122: checking build system type configure:2140: result: x86_64-unknown-freebsd7.0 [...] configure:2721: gcc -v >&5 Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] [...] objdir != srcdir, for both llvm and gcc. Release

Hello; I was able to build and install llvm(3.0) under Ubuntu 11.10 (using the ./configure script found under llvm source, and then make and make install). While configuring, I gave --prefix as a directory where I would like llvm to be installed. I did not give --with-llvmgccdir and the --enable-optimized argument to configure. Because 3.0 doesn't come with llvmgcc source/binaries and I

Does anybody know the purpose of test: projects/test-suite/SingleSource/UnitTests/SignlessTypes/ccc.c

On Oct 20, 2009, at 6:02 AM, Duncan Sands wrote: > Hi Tanya, > >> 1) Compile llvm from source and untar the llvm-test in the projects >> directory (name it llvm-test or test-suite). Choose to use a pre- >> compiled llvm-gcc or re-compile it yourself. > > I compiled llvm and llvm-gcc with separate objects directories. > Platform is x86_64-linux-gnu. > Ok.

>From the comment at the top of the file: /* * This file is used to the C calling conventions with signless * LLVM. Integer arguments in this convention are promoted to at * least a 32-bit size. Consequently signed values must be * sign extended and unsigned values must be zero extended to * at least a 32-bit integer type. */ :-) -Gordon > -----Original Message----- > From:

But read the code and then answer the question. :) On 07/25/2012 06:19 PM, Gordon Keiser wrote: > From the comment at the top of the file: > > /* > * This file is used to the C calling conventions with signless > * LLVM. Integer arguments in this convention are promoted to at > * least a 32-bit size. Consequently signed values must be > * sign extended and unsigned

Thanks to the hard work of Bill Wendling (wendling at isanbard.org), LLVM now translates setjmp/longjmp calls into the LLVM "exception handling" instructions invoke & unwind. This means that all of the LLVM optimizers are now aware of the extra control flow edges made possible by setjmp & longjmp, so data flow analyses won't make incorrect transformations. A variety of

G'Day Tanya, Is it too late to bring in the following patches to fix some major brokenness in the AuroraUX tool chain for 2.6? http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Driver/Tools.cpp?r1=84468&r2=84469&view=diff&pathrev=84469 http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Driver/Tools.cpp?r1=84265&r2=84266&view=diff&pathrev=84266

For the heck of it I tried upgrading to gcc 3.4.2 (from 3.3.3). It didn't make a difference. So here are the failures for llvm-test. All diffs are against the "native" output. ===================== MultiSource/Applications/sgefa cbe failed differently from jit/llc. First cbe: 84c84 < One-Norm(A) ---------- 8.879153e+02. --- > One-Norm(A) ---------- 8.879156e+02.

Please email the list, not me directly. Try doing a 'make clean' then a 'make VERBOSE=1' in the test-suite directory. -Chris On Jan 13, 2011, at 6:04 PM, Qingan Li wrote: > Hi Chris, > > [qali at qali SingleSource]$ llvm-gcc -v > Using built-in specs. > Target: x86_64-unknown-linux-gnu > Configured with: /home/nicholas/2.8-final/llvmgcc42-2.8.src/configure

[qali at qali test-suite]$ make VERBOSE=1 if [ ! -f SingleSource/Makefile ]; \ then \ /home/qali/Src/llvm-2.8/autoconf/mkinstalldirs SingleSource; \ cp /home/qali/Src/llvm-2.8/projects/test-suite/SingleSource/Makefile SingleSource/Makefile; \ fi; \ make -C SingleSource all make[1]: Entering directory `/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource' if [ ! -f UnitTests/Makefile