LLVM 4.0.1-rc1 has been tagged

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
Hi,

I've just tagged the 4.0.1 -rc1 release.  Testers can start testing and uploading
the binaries.  If you still have bug fixes you want to get into the
4.0.1 release, you have until May 22 to submit merge requests.

-Tom
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
Hi,

AArch64 looks good.
5c8915a58032f7efc6e9af3a1d6ff99ade3170d2
clang+llvm-4.0.1-rc1-aarch64-linux-gnu.tar.xz

Cheers,
Diana

On 2 May 2017 at 03:00, Tom Stellard via llvm-dev
<[hidden email]> wrote:

> Hi,
>
> I've just tagged the 4.0.1 -rc1 release.  Testers can start testing and uploading
> the binaries.  If you still have bug fixes you want to get into the
> 4.0.1 release, you have until May 22 to submit merge requests.
>
> -Tom
> _______________________________________________
> LLVM Developers mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
On 2 May 2017 at 15:36, Diana Picus via llvm-dev
<[hidden email]> wrote:
> Hi,
>
> AArch64 looks good.
> 5c8915a58032f7efc6e9af3a1d6ff99ade3170d2
> clang+llvm-4.0.1-rc1-aarch64-linux-gnu.tar.xz

ARMv7 looks good.
76784402233e8edbceed6d7f8e9da16f5ecfa001
clang+llvm-4.0.1-rc1-armv7a-linux-gnueabihf.tar.xz

cheers,
--renato
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
In reply to this post by Nat! via cfe-dev
On Mon, May 1, 2017 at 6:00 PM, Tom Stellard via llvm-dev
<[hidden email]> wrote:
> Hi,
>
> I've just tagged the 4.0.1 -rc1 release.  Testers can start testing and uploading
> the binaries.  If you still have bug fixes you want to get into the
> 4.0.1 release, you have until May 22 to submit merge requests.

Windows looks good:

$ sha1sum *4.0.1-rc1*.exe
30bc4caacbb112ece6ebed4329ef2ba1117b3adf  LLVM-4.0.1-rc1-win32.exe
8c6b76e9859de1b6bcd6d9e694e3a5ba1cf82043  LLVM-4.0.1-rc1-win64.exe
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
In reply to this post by Nat! via cfe-dev
On 2 May 2017, at 03:00, Tom Stellard via Release-testers <[hidden email]> wrote:
>
> I've just tagged the 4.0.1 -rc1 release.  Testers can start testing and uploading
> the binaries.  If you still have bug fixes you want to get into the
> 4.0.1 release, you have until May 22 to submit merge requests.

On FreeBSD 10/i386, I get the following test results:

======================================================================
1 warning(s) in tests.
Testing Time: 761.04s
********************
Unexpected Passing Tests (1):
    lldb :: Expr/TestCallStdStringFunction.test

********************
Failing Tests (3):
    lldb :: Expr/TestCallStopAndContinue.test
    lldb :: Expr/TestCallUserAnonTypedef.test
    lldb :: Expr/TestCallUserDefinedFunction.test

  Expected Passes    : 31135
  Expected Failures  : 178
  Unsupported Tests  : 1095
  Unexpected Passes  : 1
  Unexpected Failures: 3
gmake[3]: *** [CMakeFiles/check-all.dir/build.make:58: CMakeFiles/check-all] Error 1
gmake[3]: Target 'CMakeFiles/check-all.dir/build' not remade because of errors.
gmake[2]: *** [CMakeFiles/Makefile2:286: CMakeFiles/check-all.dir/all] Error 2
gmake[1]: *** [CMakeFiles/Makefile2:293: CMakeFiles/check-all.dir/rule] Error 2
gmake[1]: Target 'check-all' not remade because of errors.
gmake: *** [Makefile:197: check-all] Error 2
[Release Phase3] check-all failed

# Comparing Phase 2 and Phase 3 files
file TypeLocBuilder.cpp.o differs between phase 2 and phase 3
file SymbolTable.cpp.o differs between phase 2 and phase 3
file OutputSections.cpp.o differs between phase 2 and phase 3
file StringRef.cpp.o differs between phase 2 and phase 3
file asan_interceptors.cc.o differs between phase 2 and phase 3
file asan_interceptors.cc.o differs between phase 2 and phase 3
### Testing Finished ###
### Package: clang+llvm-4.0.1-rc1-i386-unknown-freebsd10.tar.xz
### Logs: /home/dim/llvm-4.0.1/rc1/logs
### Errors:
[Release Phase3] check-all failed
======================================================================

On FreeBSD 10/amd64, there are less test failures, and no phase 2/3 mismatches:

======================================================================
1 warning(s) in tests.
Testing Time: 1998.12s
********************
Unexpected Passing Tests (1):
    lldb :: Expr/TestCallStdStringFunction.test

********************
Failing Tests (1):
    ThreadSanitizer-x86_64 :: signal_reset.cc

  Expected Passes    : 32044
  Expected Failures  : 164
  Unsupported Tests  : 1674
  Unexpected Passes  : 1
  Unexpected Failures: 1
gmake[3]: *** [CMakeFiles/check-all.dir/build.make:58: CMakeFiles/check-all] Error 1
gmake[3]: Target 'CMakeFiles/check-all.dir/build' not remade because of errors.
gmake[2]: *** [CMakeFiles/Makefile2:262: CMakeFiles/check-all.dir/all] Error 2
gmake[1]: *** [CMakeFiles/Makefile2:269: CMakeFiles/check-all.dir/rule] Error 2
gmake[1]: Target 'check-all' not remade because of errors.
gmake: *** [Makefile:223: check-all] Error 2
[Release Phase3] check-all failed

# Comparing Phase 2 and Phase 3 files
### Testing Finished ###
### Package: clang+llvm-4.0.1-rc1-amd64-unknown-freebsd10.tar.xz
### Logs: /home/dim/llvm-4.0.1/rc1/logs
### Errors:
[Release Phase3] check-all failed
======================================================================

This was not significantly different from 4.0.0, so I have uploaded:

SHA256 (clang+llvm-4.0.1-rc1-i386-unknown-freebsd10.tar.xz) = deff84a8f288d80d9bfef6112bb8e8d101330dae040d363d381155a8abe5d8cc
SHA256 (clang+llvm-4.0.1-rc1-amd64-unknown-freebsd10.tar.xz) = b8d5ee45cf1486b48737837440da34d4f7e783dce10689dd0ea96bd14bf3682d

-Dimitry


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
In reply to this post by Nat! via cfe-dev
Hi,

I'm seeming new regressions form 4.0.0 for mips big endian:

    DataFlowSanitizer-mips64 :: custom.cc
    DataFlowSanitizer-mips64 :: propagate.c
    SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc
    SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard.cc
    SanitizerCommon-asan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc
    SanitizerCommon-asan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc
    SanitizerCommon-asan-mips64-Linux :: sanitizer_coverage_trace_pc_guard.cc                                          
    SanitizerCommon-lsan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc                                              
    SanitizerCommon-lsan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc                                      
    SanitizerCommon-lsan-mips64-Linux :: sanitizer_coverage_trace_pc_guard.cc                                          
    SanitizerCommon-msan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc                                      
    SanitizerCommon-msan-mips64-Linux :: sanitizer_coverage_trace_pc_guard.cc

I'm already aware of the dataflow sanitizer bug. The sanitizer_coverage_trace_pc_guard(-dso) failures for
(a, l, m)san-mips64-Linux is an occurrence of a existing failure.

Little endian and debian are ok.

I've uploaded the binaries.

SHA1(clang+llvm-4.0.1-rc1-mips-linux-gnu.tar.xz)= bd5dd8ccc1e584c6846dea2b743a4227506a8f6b
SHA1(clang+llvm-4.0.1-rc1-mipsel-linux-gnu.tar.xz)= 4cc5ad7f6ab763a8b93a3168ed6420e1db4b8052
SHA1(clang+llvm-4.0.1-rc1-x86_64-linux-gnu-debian8.tar.xz)= bac30cd1820e0a3e8abd45e5ca836ea3ef0f78dc

Thanks,
Simon
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
In reply to this post by Nat! via cfe-dev
I've updated OpenMandriva (x86_64, aarch64, x86_32, armv7hnl), no issues so far.

ttyl
bero

On 2 May 2017 at 03:00, Tom Stellard via Release-testers <[hidden email]> wrote:
Hi,

I've just tagged the 4.0.1 -rc1 release.  Testers can start testing and uploading
the binaries.  If you still have bug fixes you want to get into the
4.0.1 release, you have until May 22 to submit merge requests.

-Tom
_______________________________________________
Release-testers mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
In reply to this post by Nat! via cfe-dev


Le 02/05/2017 à 03:00, Tom Stellard via Release-testers a écrit :
> Hi,
>
> I've just tagged the 4.0.1 -rc1 release.  Testers can start testing and uploading
> the binaries.  If you still have bug fixes you want to get into the
> 4.0.1 release, you have until May 22 to submit merge requests.
>
>
All green on Debian archs! Well done!

S

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
In reply to this post by Nat! via cfe-dev
On 05/05/2017 02:37 PM, Simon Dardis wrote:

> Hi,
>
> I'm seeming new regressions form 4.0.0 for mips big endian:
>
>     DataFlowSanitizer-mips64 :: custom.cc
>     DataFlowSanitizer-mips64 :: propagate.c
>     SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc
>     SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard.cc
>     SanitizerCommon-asan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc
>     SanitizerCommon-asan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc
>     SanitizerCommon-asan-mips64-Linux :: sanitizer_coverage_trace_pc_guard.cc                                          
>     SanitizerCommon-lsan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc                                              
>     SanitizerCommon-lsan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc                                      
>     SanitizerCommon-lsan-mips64-Linux :: sanitizer_coverage_trace_pc_guard.cc                                          
>     SanitizerCommon-msan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc                                      
>     SanitizerCommon-msan-mips64-Linux :: sanitizer_coverage_trace_pc_guard.cc
>

Can you bisect to see which commit broke these tests?

-Tom

> I'm already aware of the dataflow sanitizer bug. The sanitizer_coverage_trace_pc_guard(-dso) failures for
> (a, l, m)san-mips64-Linux is an occurrence of a existing failure.
>
> Little endian and debian are ok.
>
> I've uploaded the binaries.
>
> SHA1(clang+llvm-4.0.1-rc1-mips-linux-gnu.tar.xz)= bd5dd8ccc1e584c6846dea2b743a4227506a8f6b
> SHA1(clang+llvm-4.0.1-rc1-mipsel-linux-gnu.tar.xz)= 4cc5ad7f6ab763a8b93a3168ed6420e1db4b8052
> SHA1(clang+llvm-4.0.1-rc1-x86_64-linux-gnu-debian8.tar.xz)= bac30cd1820e0a3e8abd45e5ca836ea3ef0f78dc
>
> Thanks,
> Simon
>

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
On 05/08/2017 05:41 AM, Tom Stellard via cfe-dev wrote:

> On 05/05/2017 02:37 PM, Simon Dardis wrote:
>> Hi,
>>
>> I'm seeming new regressions form 4.0.0 for mips big endian:
>>
>>     DataFlowSanitizer-mips64 :: custom.cc
>>     DataFlowSanitizer-mips64 :: propagate.c
>>     SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc
>>     SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard.cc
>>     SanitizerCommon-asan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc
>>     SanitizerCommon-asan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc
>>     SanitizerCommon-asan-mips64-Linux :: sanitizer_coverage_trace_pc_guard.cc                                          
>>     SanitizerCommon-lsan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc                                              
>>     SanitizerCommon-lsan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc                                      
>>     SanitizerCommon-lsan-mips64-Linux :: sanitizer_coverage_trace_pc_guard.cc                                          
>>     SanitizerCommon-msan-mips64-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc                                      
>>     SanitizerCommon-msan-mips64-Linux :: sanitizer_coverage_trace_pc_guard.cc
>>
>
> Can you bisect to see which commit broke these tests?
>

Did you ever figure out what caused the regressions?  Do you think these are
release blockers?

-Tom

> -Tom
>
>> I'm already aware of the dataflow sanitizer bug. The sanitizer_coverage_trace_pc_guard(-dso) failures for
>> (a, l, m)san-mips64-Linux is an occurrence of a existing failure.
>>
>> Little endian and debian are ok.
>>
>> I've uploaded the binaries.
>>
>> SHA1(clang+llvm-4.0.1-rc1-mips-linux-gnu.tar.xz)= bd5dd8ccc1e584c6846dea2b743a4227506a8f6b
>> SHA1(clang+llvm-4.0.1-rc1-mipsel-linux-gnu.tar.xz)= 4cc5ad7f6ab763a8b93a3168ed6420e1db4b8052
>> SHA1(clang+llvm-4.0.1-rc1-x86_64-linux-gnu-debian8.tar.xz)= bac30cd1820e0a3e8abd45e5ca836ea3ef0f78dc
>>
>> Thanks,
>> Simon
>>
>
> _______________________________________________
> LLVM Developers mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: LLVM 4.0.1-rc1 has been tagged

Nat! via cfe-dev
I had no luck tracking down the commit that cause Compiler-rt to change it's supported
targets for the machine I was building on. It may be due to change in the machine's
configuration.

I'm not considering them release blockers as some are  known defects partially caused by
the test machine's version of libc. The Dataflow sanitizer regression I have a posted patch
for but it hasn't gone through review yet. But the underlying bug was there for some time,
it wasn't tested.

Thanks,
Simon

> -----Original Message-----
> From: Tom Stellard [mailto:[hidden email]]
> Sent: 30 May 2017 14:41
> To: Simon Dardis
> Cc: [hidden email]; Release-testers; [hidden email]
> Subject: Re: [cfe-dev] LLVM 4.0.1-rc1 has been tagged
>
> On 05/08/2017 05:41 AM, Tom Stellard via cfe-dev wrote:
> > On 05/05/2017 02:37 PM, Simon Dardis wrote:
> >> Hi,
> >>
> >> I'm seeming new regressions form 4.0.0 for mips big endian:
> >>
> >>     DataFlowSanitizer-mips64 :: custom.cc
> >>     DataFlowSanitizer-mips64 :: propagate.c
> >>     SanitizerCommon-asan-mips-Linux ::
> sanitizer_coverage_trace_pc_guard-dso.cc
> >>     SanitizerCommon-asan-mips-Linux ::
> sanitizer_coverage_trace_pc_guard.cc
> >>     SanitizerCommon-asan-mips64-Linux ::
> Linux/getpwnam_r_invalid_user.cc
> >>     SanitizerCommon-asan-mips64-Linux ::
> sanitizer_coverage_trace_pc_guard-dso.cc
> >>     SanitizerCommon-asan-mips64-Linux ::
> sanitizer_coverage_trace_pc_guard.cc
> >>     SanitizerCommon-lsan-mips64-Linux ::
> Linux/getpwnam_r_invalid_user.cc
> >>     SanitizerCommon-lsan-mips64-Linux ::
> sanitizer_coverage_trace_pc_guard-dso.cc
> >>     SanitizerCommon-lsan-mips64-Linux ::
> sanitizer_coverage_trace_pc_guard.cc
> >>     SanitizerCommon-msan-mips64-Linux ::
> sanitizer_coverage_trace_pc_guard-dso.cc
> >>     SanitizerCommon-msan-mips64-Linux ::
> >> sanitizer_coverage_trace_pc_guard.cc
> >>
> >
> > Can you bisect to see which commit broke these tests?
> >
>
> Did you ever figure out what caused the regressions?  Do you think these are
> release blockers?
>
> -Tom
>
> > -Tom
> >
> >> I'm already aware of the dataflow sanitizer bug. The
> >> sanitizer_coverage_trace_pc_guard(-dso) failures for (a, l, m)san-mips64-
> Linux is an occurrence of a existing failure.
> >>
> >> Little endian and debian are ok.
> >>
> >> I've uploaded the binaries.
> >>
> >> SHA1(clang+llvm-4.0.1-rc1-mips-linux-gnu.tar.xz)=
> >> bd5dd8ccc1e584c6846dea2b743a4227506a8f6b
> >> SHA1(clang+llvm-4.0.1-rc1-mipsel-linux-gnu.tar.xz)=
> >> 4cc5ad7f6ab763a8b93a3168ed6420e1db4b8052
> >> SHA1(clang+llvm-4.0.1-rc1-x86_64-linux-gnu-debian8.tar.xz)=
> >> bac30cd1820e0a3e8abd45e5ca836ea3ef0f78dc
> >>
> >> Thanks,
> >> Simon
> >>
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > [hidden email]
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev