Vasileios Kalintiris via llvm-dev
2016-Aug-04 14:12 UTC
[llvm-dev] [Release-testers] [3.9 Release] Release Candidate 1 has been tagged
clang+llvm-3.9.0-rc1-x86_64-linux-gnu-debian8.tar.xz (sha1sum
fac48e3ce11ff738c19497f2d06252aad16a6033)
Native:
All ok.
Cross compilation to various MIPS targets:
All ok.
clang+llvm-3.9.0-rc1-mips-linux-gnu.tar.xz (sha1sum
a77fd6910ce322863a5936657c1c34f4c369e8d7)
I get 38 check-all failures but only one new regression compared to 3.8.1,
ie. MemorySanitizer-mips64 :: fork.cc (I'm told that D23107 fixes this).
The failures fall into two categories 64-bit atomics tests not linking to
libatomic, and 64-bit sanitizers. The 64-bit sanitizer tests should XFAIL
based on the effective target, there's a patch pending review that adds
support for this (D22802).
AddressSanitizer-mips64-linux :: TestCases/Linux/local_alias.cc
AddressSanitizer-mips64-linux :: TestCases/Linux/odr-violation.cc
DataFlowSanitizer-mips64 :: custom.cc
DataFlowSanitizer-mips64 :: propagate.c
MemorySanitizer-mips64 :: fork.cc
SanitizerCommon-asan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc
SanitizerCommon-lsan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc
ThreadSanitizer-mips64 :: ignore_lib4.cc
ThreadSanitizer-mips64 :: longjmp.cc
ThreadSanitizer-mips64 :: longjmp2.cc
ThreadSanitizer-mips64 :: longjmp3.cc
ThreadSanitizer-mips64 :: longjmp4.cc
ThreadSanitizer-mips64 :: map32bit.cc
ThreadSanitizer-mips64 :: signal_longjmp.cc
libc++ :: std/atomics/atomics.types.generic/integral.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_strong.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_strong_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_weak.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_weak_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_exchange.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_exchange_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_add.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_add_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_and.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_and_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_or.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_or_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_sub.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_sub_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_xor.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_xor_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_init.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_is_lock_free.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_load.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_load_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_store.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_store_explicit.pass.cpp
libc++ ::
std/atomics/atomics.types.operations/atomics.types.operations.req/ctor.pass.cpp
clang+llvm-3.9.0-rc1-mipsel-linux-gnu.tar.xz (sha1sum
ab936eed817d83f8203010b892be0eef76813a15)
I get the same libc++ failures as the mips-linux-gnu build above but these
aren't regressions. However, there are two additional check-all
failures:
(1)
std/experimental/filesystem/fs.op.funcs/fs.op.last_write_time/last_write_time.pass.cpp
(2) std/numerics/complex.number/complex.transcendentals/asin.pass.cpp
(2) is a new regression which I'm investigating. I don't get the
MIPS64
sanitizer failures because this is still disabled on this machine (the
necessary multilibs aren't present).
-Vasileios
________________________________
From: Release-testers [release-testers-bounces at lists.llvm.org] on behalf of
Nikola Smiljanic via Release-testers [release-testers at lists.llvm.org]
Sent: 03 August 2016 13:32
To: Hans Wennborg
Cc: Release-testers
Subject: Re: [Release-testers] [3.9 Release] Release Candidate 1 has been tagged
Fedora x64 looking good.
On x86 I'm getting an error about missing libclang_rt.asan_cxx-i686.a when
running check-all, does anyone know what this is?
On Sat, Jul 30, 2016 at 8:57 AM, Hans Wennborg via Release-testers
<release-testers at lists.llvm.org<mailto:release-testers at
lists.llvm.org>> wrote:
Dear testers,
3.9.0-rc1 was just tagged from the 3.9 branch at r277207.
This took a little longer than I'd hoped, but I think the branch is in
a decent state now.
There are still open merge requests and bugs, but I'd like to get the
real testing started to see where we're at.
Please build, test, and upload binaries to the sftp. Let me know how
it goes. I'll upload source, docs, and your binaries to the
pre-release page once they're ready.
Thanks,
Hans
_______________________________________________
Release-testers mailing list
Release-testers at lists.llvm.org<mailto:Release-testers at
lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160804/8fa30d92/attachment.html>