2.0 Pre-release tarballs online

I've uploaded the 2.0 pre-release to this location:
http://llvm.org/prereleases/2.0/

If you have free time and would like to help test this release, please download the appropriate tarballs from the website.

Here are a few ways you can help test this release:

1) Download llvm-gcc4 binary and llvm. Compile and run make check.

2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run make check, and do "make ENABLE_OPTIMIZED=1 TEST=nightly report" in llvm-test.

3) Compile llvm-gcc4 and llvm from source. Run 'make check'.

4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test.

It would also be helpful for someone to compile/test with objdir != srcdir.
The 2.0 release defaults to a Release build, but you are welcome to test with a Debug build as well.

When reporting your results, please email the list and mention what platform, which option you chose (1, 2, 3, or 4), and if you made any configure changes (objdir != srcdir, or Debug build). Include the dejagnu test log or the nightly test report.

Thanks,
Tanya Lattner

I forgot to mention that all testing should be completed by May 20th 5pm PDT.

-Tanya

Tanya,

I have done make check and nightly report tests on LLVM on the GCC 4.2.0 release, on Linux x86 32 bit.

On make check the bit intrinsics test is still failing but it works from the command line, strange ?

What files do you want from the nightly report, as I am not familiar with it ?

I will be doing Cygwin tests next.

Aaron

Aaron,

Tanya,

I have done make check and nightly report tests on LLVM on the GCC 4.2.0
release, on Linux x86 32 bit.

On make check the bit intrinsics test is still failing but it works from the
command line, strange ?

Can you be a bit more specific about which test is failing?

Reid.

Aaron,

Tanya,

I have done make check and nightly report tests on LLVM on the GCC 4.2.0
release, on Linux x86 32 bit.

On make check the bit intrinsics test is still failing but it works from the
command line, strange ?

Can you be a bit more specific about which test is failing?

Running /usr/src/llvm/test/CodeGen/Generic/dg.exp ...
FAIL: /usr/src/llvm/test/CodeGen/Generic/bit-intrinsics.ll
Failed with signal(SIGSEGV) at line 2
while running: lli --force-interpreter=true Output/bit-intrinsics.ll.tmp.bc
lli[0x84717fc]

Chris looked at this and we found the test works fine when done separately from the command line.

Aaron

This is on FreeBSD 6.2-RELEASE, on i386.
Both llvm and llvm-gcc were compiled with objdir != srcdir.
Release, not Debug build of LLVM.

http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-make-check.txt
http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-report.nightly.txt

--Emil

4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make
ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test.

It would also be helpful for someone to compile/test with objdir != srcdir.

This is on FreeBSD 6.2-RELEASE, on i386.
Both llvm and llvm-gcc were compiled with objdir != srcdir.
Release, not Debug build of LLVM.

http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-make-check.txt
http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-report.nightly.txt

Thank you so much for testing the release!! I've checked out the nightly test report and it looks like there is potentially one regression.
SingleSource/UnitTests/Vector/SSE/sse.expandfft

However, I need you to look at your /proc/cpuinfo (or whatever it is on FreeBSD) to tell me what flavors of sse you have (mmx, sse1, sse2, etc).

Thanks,
Tanya

>> 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make
>> ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test.
>>
>> It would also be helpful for someone to compile/test with objdir != srcdir.
>
> This is on FreeBSD 6.2-RELEASE, on i386.
> Both llvm and llvm-gcc were compiled with objdir != srcdir.
> Release, not Debug build of LLVM.
>
> http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-make-check.txt
> http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-report.nightly.txt

Thank you so much for testing the release!!

You're welcome!

I've checked out the nightly test report and it looks like there is
potentially one regression.
SingleSource/UnitTests/Vector/SSE/sse.expandfft

However, I need you to look at your /proc/cpuinfo (or whatever it is

CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.12-MHz 686-class CPU)
  Origin = "GenuineIntel" Id = 0xf34 Stepping = 4
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x441d<SSE3,RSVD2,MON,DS_CPL,CNTX-ID,<b14>>

Looks like 1, 2, _and_ 3 are supported.

<b14> is xTPR (Send Task Priority Messages)

--Emil

Okay, this is probably some stack alignment issue or something. Can you please file a bug? This is not a 2.0 blocker, but we want to track it.

Thanks!

-Chris

On make check the bit intrinsics test is still failing but it works from the
command line, strange ?

Did Chris help you with this or is it still an issue?

What files do you want from the nightly report, as I am not familiar with it
?

in llvm-test, if you run the gmake TEST=nightly report command it will generated a report.nightly.txt file. Thats what I want to see.

Thanks!

-Tanya

On make check the bit intrinsics test is still failing but it works from the
command line, strange ?

Did Chris help you with this or is it still an issue?

We did not resolve it.

What files do you want from the nightly report, as I am not familiar with it
?

in llvm-test, if you run the gmake TEST=nightly report command it will
generated a report.nightly.txt file. Thats what I want to see.

The results on LLVM Test Results on mailing list.

Cheers,

Aaron

On make check the bit intrinsics test is still failing but it works from the
command line, strange ?

Did Chris help you with this or is it still an issue?

Yes, but we did not resolve it, its trivial anyway, time better spent else where.

What files do you want from the nightly report, as I am not familiar with it
?

in llvm-test, if you run the gmake TEST=nightly report command it will
generated a report.nightly.txt file. Thats what I want to see.

Okay test results on the LLVM Test results mailing list.

Doing Cygwin tests now.

Thanks,

Aaron

I've updated the pre-release tarballs online. I'm also extending the testing completion date to May 22nd at 5pm PDT. The new release target date is May 23rd.

If you have any free time, please give the new pre-release a try.

Thanks to all who have tested LLVM!

-Tanya

P.S. Documentation review should still be completed today! Thanks!

Sure thing: http://llvm.org/bugs/show_bug.cgi?id=1438

Sorry if I got the product / category / whatever wrong.
Bugzilla always confuses me. =(

--Emil

Just a reminder, if anyone is still testing, please send me your results by 5pm PDT Today!

At this point, it looks like the release is on schedule for Wednesday. We won't be delaying it unless new test results reveal major problems.

Thanks for all your help,
Tanya