similar to: [LLVMdev] nightly test suite failure: ms_struct-bitfield-init-1.c

On May 6, 2011, at 1:29 AM, Jay Foad wrote: > Hi, > > I've just tried to run the test-suite, for the first time in ages. It > stops rather abruptly with: > > $ make TEST=nightly report report.html This is a test that Fariborz has been working on with Clang. It is possible that llvm-gcc is expected to fail it, if this is so, the test can be put in an #ifdef __clang__.

On 6 May 2011 09:29, Jay Foad <jay.foad at gmail.com> wrote: > I've just tried to run the test-suite, for the first time in ages. It > stops rather abruptly with: > > $ make TEST=nightly report report.html > > /home/jay/llvm/local/bin/llvm-gcc > -I/home/jay/llvm/gitobjdir/projects/test-suite/SingleSource/UnitTests >

On 15 June 2011 09:37, Jay Foad <jay.foad at gmail.com> wrote: > On 6 May 2011 09:29, Jay Foad <jay.foad at gmail.com> wrote: >> I've just tried to run the test-suite, for the first time in ages. It >> stops rather abruptly with: >> >> $ make TEST=nightly report report.html >> >> /home/jay/llvm/local/bin/llvm-gcc >>

On May 6, 2011, at 4:57 PM, Andrew Trick wrote: > On May 6, 2011, at 1:29 AM, Jay Foad wrote: > >> This seems wrong -- if a test fails, it shouldn't stop the whole >> "make", it should just get logged as a failure and continue. > > That's a frustrating aspect of the test-suite Makefiles. I don't know how to work around it without removing the test

Fariborz, On May 6, 2011, at 5:07 PM, Fariborz Jahanian wrote: > > On May 6, 2011, at 4:57 PM, Andrew Trick wrote: > >> On May 6, 2011, at 1:29 AM, Jay Foad wrote: >> >>> This seems wrong -- if a test fails, it shouldn't stop the whole >>> "make", it should just get logged as a failure and continue. >> >> That's a

On May 6, 2011, at 1:29 AM, Jay Foad wrote: > This seems wrong -- if a test fails, it shouldn't stop the whole > "make", it should just get logged as a failure and continue. That's a frustrating aspect of the test-suite Makefiles. I don't know how to work around it without removing the test from your tree. -Andy

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

> So how about the attached patch? OK to commit? Or here's a different way of patching it, if you prefer. Thanks, Jay. -------------- next part -------------- A non-text attachment was scrubbed... Name: pragma-ms-struct-2 Type: application/octet-stream Size: 989 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110615/a1ebe3af/attachment.obj>

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 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. 2) Run make check,

> The patch looks fine to me, does it pass regression tests etc? Yes, I've just run a successful "make" in the test-suite module. It took hours! Is there a smaller set of regression tests I could run for changes like this in future? Thanks, Jay.

I've built a debug build of llvm 2.6, and llvm-gcc 2.6 for arm-elf with --enable-checking=yes. On the attached test case (which is g++.dg/expr/bitfield4.C from the GCC 4.2 testsuite) I get: $ cc1plus bitfield4.ii -emit-llvm-bc -o bitfield4.o -quiet cc1plus: /home/foad/svn/antix/toolchain/branches/w/foad/2757llvm26/toolchain/llvm/llvm-gcc/gcc/llvm-convert.cpp:999: llvm::Value*

On 7 November 2011 22:00, Bill Wendling <wendling at apple.com> wrote: > We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: > >        http://llvm.org/pre-releases/3.0/rc3/ > > for the sources. There are also binaries for Darwin up there, with more to come during the week. Please build this release candidate, test it out on your

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

Good day, LLVMers! We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: http://llvm.org/pre-releases/3.0/rc3/ for the sources. There are also binaries for Darwin up there, with more to come during the week. Please build this release candidate, test it out on your projects, and let us know if you find any regressions from the 2.9 release. Please keep

On Mon, Apr 27, 2009 at 9:45 AM, Jay Foad <jay.foad at gmail.com> wrote: > > The patch looks fine to me, does it pass regression tests etc? > > Yes, I've just run a successful "make" in the test-suite module. It > took hours! Is there a smaller set of regression tests I could run for > changes like this in future? "make unittests" is a smaller set

LLVMers, The 2.5 pre-release is available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run "make

LLVMers, The 2.2 prerelease is now available for testing: http://llvm.org/prereleases/2.2/ If anyone can help test this release, I ask that you do the following: 1) Build llvm and llvm-gcc (or use a binary). You may build release (default) or debug. You may pick llvm-gcc-4.0, llvm-gcc-4.2, or both. 2) Run 'make check'. 3) In llvm-test, run 'make TEST=nightly report'. 4) When

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. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to

LLVMers, The 2.1 pre-release (version 1) is available for testing: http://llvm.org/prereleases/2.1/version1/ I'm looking for members of the LLVM community to test the 2.1 release. There are 2 ways you can help: 1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0 binary. Run "make check" and the full llvm-test suite (make TEST=nightly report). 2) Download

On Nov 8, 2011, at 7:18 AM, Jay Foad wrote: > On 7 November 2011 22:00, Bill Wendling <wendling at apple.com> wrote: >> We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: >> >> http://llvm.org/pre-releases/3.0/rc3/ >> >> for the sources. There are also binaries for Darwin up there, with more to come during