2.2 Prerelease available for testing

Project Infrastructure LLVM Dev List Archives
1

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 submitting your testing results to the list, please include:
   - Target
   - How you built the release (objDir = srcDir? Release? Debug?
           llvm-gcc binary?)
   - Which llvm-gcc you used.
   - make check results (either final totals or log file)
   - llvm-test results (report.nightly.txt)

All prerelease testing must be completed by Feb 1, 2008.

The release has been delayed by one week, and I have updated the schedule on the main page. Here is the new schedule:
* Jan 24, 2008: First round of pre-release testing begins.
* Feb 1, 2008: Pre-release testing ends.
* Feb 3, 2008: Second round of pre-release testing begins.
* Feb 10, 2008: Pre-release testing ends.
* Feb 11, 2008: 2.2 released.

Thanks,
Tanya Lattner

2

My test results for the LLVM 2.2 prerelease.

=== Q. Target ===

* Mac OS X 10.4.11
* 2 GHz Intel Core 2 Duo
* MacBook

% uname -a
  Darwin macbook.local 8.11.1 Darwin Kernel Version 8.11.1:
  Wed Oct 10 18:23:28 PDT 2007;
  root:xnu-792.25.20~1/RELEASE_I386 i386 i386

=== Q. How you built the release ===

* objDir != srcDir
* Release build
* llvm-gcc-4.2 from source (llvm-gcc4.2-2.2.source.tar.gz)

=== Q. Which llvm-gcc you used. ===

* llvm-gcc-4.2 from source (llvm-gcc4.2-2.2.source.tar.gz)

=== Q. make check results (either final totals or log file) ===

* Attachment (testrun.log)

=== Q. lvm-test results (report.nightly.txt) ===

* Attachment (llvm-test-2.2.txt)

I also put a detailed build instructions here.

  http://metareal.jottit.com/llvm-2.2-prerelease

Hope this help.

logs.tar.gz (64.1 KB)

3

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 build (I tried a Debug+Checks but it blew up in the xgcc stage).
llvm-gcc 4.2 from source.

I did:

$ cd /home/llvm
$ mkdir obj-llvm
$ cd obj-llvm
$ ../llvm-2.2/configure --prefix=/home/llvm/local
$ gmake

$ cd ..
$ mkdir obj-gcc
$ cd obj-gcc
$ ../llvm-gcc4.2-2.2.source/configure --prefix=/home/llvm/local \
  --enable-llvm=/home/llvm/obj-llvm --program-prefix=llvm- \
  --enable-languages=c,c++ --disable-shared
  # ^^ shared libraries not happy on amd64 yet?
$ gmake
$ gmake install

$ cd ../obj-llvm
$ ../llvm-2.2/configure --with-llvmgccdir=/home/llvm/local \
  --prefix=/home/llvm/local
$ gmake
$ gmake check
[...]
                === Summary ===

# of expected passes 2519
# of unexpected failures 1
# of expected failures 7
gmake[1]: *** [check-local] Error 1

The unexpected failure was:
Running /home/llvm/llvm-2.2/test/CFrontend/dg.exp ...
FAIL: /home/llvm/llvm-2.2/test/CFrontend/2007-09-12-PragmaPack.c
Failed with exit(1) at line 1
while running: /home/llvm/local/bin/llvm-gcc -emit-llvm -O3 -S -o - /home/llvm/llvm-2.2/test/CFrontend/2007-09-12-PragmaPack.c | grep {26}
child process exited abnormally
Running /home/llvm/llvm-2.2/test/CodeGen/ARM/dg.exp ...

$ cd ../llvm-test-2.2
$ ./configure --prefix=/home/llvm/local \
  --with-llvmsrc=/home/llvm/llvm-2.2 --with-llvmobj=/home/llvm/obj-llvm
$ gmake TEST=nightly report

The report.nightly.txt is attached.

I had to manually kill minisat after it burned >20mins CPU time. Reid
and I fixed time limits in RunSafely.sh 1.31 (back in the CVS days) but
the change does not appear in the llvm-test tarball.

Reid's commit was:
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070514/049803.html

--Emil

report.nightly.txt (66.3 KB)

4

Thanks for testing the release. Overall the test results look decent with a couple exceptions.

You also have a few CBE failures that I am not seeing. What version of xcode do you have installed?

Can you send me the following files?
SingleSource/Regression/C/Output/2008-01-07-LongDouble.*
SingleSource/Regression/C/Output/PR1386.*

Thanks,
Tanya

5

First, thanks for testing the release.

A couple comments.

                === Summary ===

# of expected passes 2519
# of unexpected failures 1
# of expected failures 7
gmake[1]: *** [check-local] Error 1

The unexpected failure was:
Running /home/llvm/llvm-2.2/test/CFrontend/dg.exp ...
FAIL: /home/llvm/llvm-2.2/test/CFrontend/2007-09-12-PragmaPack.c
Failed with exit(1) at line 1
while running: /home/llvm/local/bin/llvm-gcc -emit-llvm -O3 -S -o - /home/llvm/llvm-2.2/test/CFrontend/2007-09-12-PragmaPack.c | grep {26}
child process exited abnormally
Running /home/llvm/llvm-2.2/test/CodeGen/ARM/dg.exp ...

This is a bug in the test case, thanks for bringing it to our attention. It will be fixed on mainline and the release.

$ cd ../llvm-test-2.2
$ ./configure --prefix=/home/llvm/local \
  --with-llvmsrc=/home/llvm/llvm-2.2 --with-llvmobj=/home/llvm/obj-llvm
$ gmake TEST=nightly report

The report.nightly.txt is attached.

A lot of these are known failures. But there are a few exceptions.

Can you bugpoint MultiSource/Benchmarks/MiBench/security-rijndael/security-rijndael?
% cd MultiSource/Benchmarks/MiBench/security-rijndael/security-rijndael
% make bugpoint-llc

Then file a bugzilla with the output.

If that doesn't work, can you try bugpointing MultiSource/Applications/SPASS/SPASS (the same way as above)?

I had to manually kill minisat after it burned >20mins CPU time. Reid
and I fixed time limits in RunSafely.sh 1.31 (back in the CVS days) but
the change does not appear in the llvm-test tarball.

Reid's commit was:
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070514/049803.html

That patch was reverted because it did not work on Darwin. This is really a bug in minisat and hopefully bugpointing the other two will also fix this.

-Tanya

6

Dear Tanya:

You also have a few CBE failures that I am not seeing. What version
of xcode do you have installed?

Xcode 2.4.1

Can you send me the following files?
SingleSource/Regression/C/Output/2008-01-07-LongDouble.*
SingleSource/Regression/C/Output/PR1386.*

OK, I attached those files (llvm-2.2-test-output.tar.gz)

Best regards,

llvm-2.2-test-output.tar.gz (18 KB)

7

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.

LLVM's "gmake check" summary:
  # of expected passes 2520
  # of expected failures 7

The llvm-test nightly report is attached.
I had to manually kill tramp3d-v4.native after ~1hr of CPU time.

--Emil

report.nightly.txt (66.9 KB)

8

FWIW, I think it makes sense to remove tramp3d-v4 from the 2.2 branch.

-Chris

9

Apparently not. =( bugpoint tries to create a shared object, which
isn't working on amd64.

--Emil

10

Dear Tanya:

You also have a few CBE failures that I am not seeing. What version
of xcode do you have installed?

Xcode 2.4.1

Same as mine.

Can you send me the following files?
SingleSource/Regression/C/Output/2008-01-07-LongDouble.*
SingleSource/Regression/C/Output/PR1386.*

OK, I attached those files (llvm-2.2-test-output.tar.gz)

Thanks. After reviewing these, it looks like there was something wrong with your native compiler. For example, your output for 2008-01-07-LongDouble/2008-01-07-LongDouble.out-nat is wrong.

I'm not sure what happened here, but its not in llvm because your llc output is correct. It reports a failure because it compares your llc output to your native output (which is wrong).

Thanks,
Tanya