thr3ads.net - llvm dev - [llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing! [Nov 2015]

If this information is useful, please help other people find it:
Share via:

Tom Stellard via llvm-dev

2015-Nov-17 03:32 UTC

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

Hi,

I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
reminder, when doing regression testing, use the 3.7.0 release
as your baseline.

Thanks,
Tom

Renato Golin via llvm-dev

2015-Nov-17 15:08 UTC

head link

[llvm-dev] [cfe-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

On 17 November 2015 at 03:32, Tom Stellard via cfe-dev
<cfe-dev at lists.llvm.org> wrote:> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> reminder, when doing regression testing, use the 3.7.0 release
> as your baseline.
Hi Tom,

ARM and AArch64 built, checked and uploaded. Al green.

cheers,
--renato

Russell Wallace via llvm-dev

2015-Nov-17 15:32 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

Tried downloading and building on Windows x64. No obvious error messages
and some LLVM binaries were built, but clang was not. Has something changed
in the build procedure? This is the script I used:

svn co http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_371/rc1 llvm-svn
cd llvm/tools
svn co http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_371/rc1 llvm-svn

cd \llvm-svn
if errorlevel 1 goto :eof
md build
if errorlevel 1 goto :eof
cd build
if errorlevel 1 goto :eof

if "%VCINSTALLDIR%"=="" call "C:\Program Files
(x86)\Microsoft Visual
Studio 14.0\VC\vcvarsall" x64
if errorlevel 1 goto :eof

\CMake\bin\cmake.exe -DLLVM_ENABLE_TIMESTAMPS=OFF -DLLVM_USE_CRT_DEBUG=MTd
-DLLVM_USE_CRT_RELEASE=MT -DPYTHON_EXECUTABLE=C:\Python27\python.exe -G
"Visual Studio 14 Win64" ..
if errorlevel 1 goto :eof

msbuild /t:clean,build ALL_BUILD.vcxproj
if errorlevel 1 goto :eof
msbuild /p:Configuration=Release /t:clean,build /fileLogger
ALL_BUILD.vcxproj
if errorlevel 1 goto :eof


On Tue, Nov 17, 2015 at 3:32 AM, Tom Stellard <tom at stellard.net> wrote:
> Hi,
>
> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> reminder, when doing regression testing, use the 3.7.0 release
> as your baseline.
>
> Thanks,
> Tom
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151117/531fe848/attachment.html>

Russell Wallace via llvm-dev

2015-Nov-17 15:37 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

... oops, my bad, I just noticed when looking over the email that I made a
mistake in adapting my usual build script to build the release candidate,
it uses an incorrect directory name. I'll retry with that fixed.

On Tue, Nov 17, 2015 at 3:32 PM, Russell Wallace <russell.wallace at
gmail.com>
wrote:
> Tried downloading and building on Windows x64. No obvious error messages
> and some LLVM binaries were built, but clang was not. Has something changed
> in the build procedure? This is the script I used:
>
> svn co http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_371/rc1 llvm-svn
> cd llvm/tools
> svn co http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_371/rc1 llvm-svn
>
> cd \llvm-svn
> if errorlevel 1 goto :eof
> md build
> if errorlevel 1 goto :eof
> cd build
> if errorlevel 1 goto :eof
>
> if "%VCINSTALLDIR%"=="" call "C:\Program Files
(x86)\Microsoft Visual
> Studio 14.0\VC\vcvarsall" x64
> if errorlevel 1 goto :eof
>
> \CMake\bin\cmake.exe -DLLVM_ENABLE_TIMESTAMPS=OFF -DLLVM_USE_CRT_DEBUG=MTd
> -DLLVM_USE_CRT_RELEASE=MT -DPYTHON_EXECUTABLE=C:\Python27\python.exe -G
> "Visual Studio 14 Win64" ..
> if errorlevel 1 goto :eof
>
> msbuild /t:clean,build ALL_BUILD.vcxproj
> if errorlevel 1 goto :eof
> msbuild /p:Configuration=Release /t:clean,build /fileLogger
> ALL_BUILD.vcxproj
> if errorlevel 1 goto :eof
>
>
> On Tue, Nov 17, 2015 at 3:32 AM, Tom Stellard <tom at stellard.net>
wrote:
>
>> Hi,
>>
>> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
>> reminder, when doing regression testing, use the 3.7.0 release
>> as your baseline.
>>
>> Thanks,
>> Tom
>>
>
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151117/593348f1/attachment.html>

Hans Wennborg via llvm-dev

2015-Nov-17 21:10 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

On Mon, Nov 16, 2015 at 7:32 PM, Tom Stellard <tom at stellard.net>
wrote:> Hi,
>
> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> reminder, when doing regression testing, use the 3.7.0 release
> as your baseline.
32-bit Windows looks fine, but I hit an assert during the lit tests
for 64-bit Windows (below).

Reid, could this be related to your recent merges? Note that while we
switched the weekly snapshots over to target msvc-style Windows
recently, 3.7 still targets mingw by default, so the 64-bit build is
using x86_64-w64-mingw32.

 - Hans



FAIL: Clang :: CodeGen/libcalls-fno-builtin.c (1715 of 8372)
******************** TEST 'Clang :: CodeGen/libcalls-fno-builtin.c'
FAILED *****
***************
Script:
--
D:/src/llvm_release_build_3.7.1-rc1/build64/./bin/clang.EXE -cc1 -internal-isyst
em D:\src\llvm_release_build_3.7.1-rc1\build64\bin\..\lib\clang\3.7.1\include -n
ostdsysteminc -S -O3 -fno-builtin -o - D:\src\llvm_release_build_3.7.1-rc1\llvm\
tools\clang\test\CodeGen\libcalls-fno-builtin.c | D:/src/llvm_release_build_3.7.
1-rc1/build64/./bin\FileCheck.EXE D:\src\llvm_release_build_3.7.1-rc1\llvm\tools
\clang\test\CodeGen\libcalls-fno-builtin.c
--
Exit Code: 2

Command Output (stdout):
--
Command 0:
"D:/src/llvm_release_build_3.7.1-rc1/build64/./bin/clang.EXE"
"-cc1"
"-internal-isystem"
"D:\src\llvm_release_build_3.7.1-rc1\build64\bin\..\lib\clan
g\3.7.1\include" "-nostdsysteminc" "-S" "-O3"
"-fno-builtin" "-o" "-" "D:\src\ll
vm_release_build_3.7.1-rc1\llvm\tools\clang\test\CodeGen\libcalls-fno-builtin.c"

Command 0 Result: -2147483645
Command 0 Output:


Command 0 Stderr:
Assertion failed: !retAI.getIndirectAlign() && "Align unused on
indirect return.
", file
D:\src\llvm_release_build_3.7.1-rc1\llvm\tools\clang\lib\CodeGen\CGCall.
cpp, line 1283

Reid Kleckner via llvm-dev

2015-Nov-17 21:41 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

John removed the assertion in his major alignment tracking patch. I
manually did that on the branch in r253380.

On Tue, Nov 17, 2015 at 1:10 PM, Hans Wennborg <hans at chromium.org>
wrote:
> On Mon, Nov 16, 2015 at 7:32 PM, Tom Stellard <tom at stellard.net>
wrote:
> > Hi,
> >
> > I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> > reminder, when doing regression testing, use the 3.7.0 release
> > as your baseline.
>
> 32-bit Windows looks fine, but I hit an assert during the lit tests
> for 64-bit Windows (below).
>
> Reid, could this be related to your recent merges? Note that while we
> switched the weekly snapshots over to target msvc-style Windows
> recently, 3.7 still targets mingw by default, so the 64-bit build is
> using x86_64-w64-mingw32.
>
>  - Hans
>
>
>
> FAIL: Clang :: CodeGen/libcalls-fno-builtin.c (1715 of 8372)
> ******************** TEST 'Clang :: CodeGen/libcalls-fno-builtin.c'
FAILED
> *****
> ***************
> Script:
> --
> D:/src/llvm_release_build_3.7.1-rc1/build64/./bin/clang.EXE -cc1
> -internal-isyst
> em
> D:\src\llvm_release_build_3.7.1-rc1\build64\bin\..\lib\clang\3.7.1\include
> -n
> ostdsysteminc -S -O3 -fno-builtin -o -
> D:\src\llvm_release_build_3.7.1-rc1\llvm\
> tools\clang\test\CodeGen\libcalls-fno-builtin.c |
> D:/src/llvm_release_build_3.7.
> 1-rc1/build64/./bin\FileCheck.EXE
> D:\src\llvm_release_build_3.7.1-rc1\llvm\tools
> \clang\test\CodeGen\libcalls-fno-builtin.c
> --
> Exit Code: 2
>
> Command Output (stdout):
> --
> Command 0:
"D:/src/llvm_release_build_3.7.1-rc1/build64/./bin/clang.EXE"
> "-cc1"
> "-internal-isystem"
> "D:\src\llvm_release_build_3.7.1-rc1\build64\bin\..\lib\clan
> g\3.7.1\include" "-nostdsysteminc" "-S"
"-O3" "-fno-builtin" "-o" "-"
> "D:\src\ll
>
>
vm_release_build_3.7.1-rc1\llvm\tools\clang\test\CodeGen\libcalls-fno-builtin.c"
>
> Command 0 Result: -2147483645
> Command 0 Output:
>
>
> Command 0 Stderr:
> Assertion failed: !retAI.getIndirectAlign() && "Align unused
on indirect
> return.
> ", file
> D:\src\llvm_release_build_3.7.1-rc1\llvm\tools\clang\lib\CodeGen\CGCall.
> cpp, line 1283
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151117/e5efc793/attachment.html>

Russell Wallace via llvm-dev

2015-Nov-18 03:50 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

Okay, LLVM and clang build and pass basic smoke test on Windows x64. What's
the procedure for running the test suite? I found a document that refers to
llvm-gcc so is presumably out of date - it says test-suite is a separate
download, is that also out of date? The normal LLVM download does contain a
lot of test code.

On Tue, Nov 17, 2015 at 3:32 AM, Tom Stellard <tom at stellard.net> wrote:
> Hi,
>
> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> reminder, when doing regression testing, use the 3.7.0 release
> as your baseline.
>
> Thanks,
> Tom
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151118/9d177e7d/attachment.html>

Nikola Smiljanic via llvm-dev

2015-Nov-18 04:57 UTC

head link

[llvm-dev] [cfe-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

We never had the official procedure for Windows, test-release.sh
script that we're using on other platforms checks out everything
that's needed and does a three phase bootstrap and runs tests that
you're referring to. We run the test-suite manually using lnt as
explained here http://llvm.org/docs/lnt/quickstart.html

On Wed, Nov 18, 2015 at 2:50 PM, Russell Wallace via cfe-dev
<cfe-dev at lists.llvm.org> wrote:> Okay, LLVM and clang build and pass basic smoke test on Windows x64.
What's
> the procedure for running the test suite? I found a document that refers to
> llvm-gcc so is presumably out of date - it says test-suite is a separate
> download, is that also out of date? The normal LLVM download does contain a
> lot of test code.
>
> On Tue, Nov 17, 2015 at 3:32 AM, Tom Stellard <tom at stellard.net>
wrote:
>>
>> Hi,
>>
>> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
>> reminder, when doing regression testing, use the 3.7.0 release
>> as your baseline.
>>
>> Thanks,
>> Tom
>
>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>

Dimitry Andric via llvm-dev

2015-Nov-18 07:55 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

On 17 Nov 2015, at 04:32, Tom Stellard <tom at stellard.net>
wrote:> 
> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> reminder, when doing regression testing, use the 3.7.0 release
> as your baseline.
Built and tested OK on FreeBSD 10.  Uploaded:

SHA256 (clang+llvm-3.7.1-rc1-amd64-unknown-freebsd10.tar.xz) =
62a365550deb5a004ea9006c17ccc2cc1a4982edce1adee292570e52b29080c7
SHA256 (clang+llvm-3.7.1-rc1-i386-unknown-freebsd10.tar.xz) =
4764228a7dfddbd7ebf862afdef49302c52176b63627957fe97ece0bf3c9446f

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151118/d0c4c8b2/attachment.sig>

Ben Pope via llvm-dev

2015-Nov-18 15:47 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

On Tuesday, November 17, 2015 11:32 AM, Tom Stellard
wrote:> Hi,
>
> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> reminder, when doing regression testing, use the 3.7.0 release
> as your baseline.
Ubuntu 15.10 x64 uploaded:
clang+llvm-3.7.1-rc1-x86_64-linux-gnu-ubuntu-15.10.tar.xz

The regression run seems very good compared to the 3.7.0 run (I have a 
faster SSD now, which may be relevant, I'll rerun the tests another 
time), but PolyBench may have some significant regressions.
Performance Regressions     18     0
Performance Improvements     463     0
Unchanged Tests     1013     1494
*Total Tests*     *1494*


Performance Regressions - Execution Time     Δ ▴     Previous 
Current     σ     Δ (B)     σ (B)
SingleSource/Benchmarks/Polybench/datamining/correlation/correlation 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.193=3> 
357.01%     0.9829     4.4920     -     0.00%     -
SingleSource/Benchmarks/Polybench/datamining/covariance/covariance 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.28=3> 
292.68%     1.1368     4.4640     -     0.00%     -
SingleSource/Benchmarks/Polybench/linear-algebra/solvers/durbin/durbin 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.284=3> 
156.05%     0.1406     0.3600     -     0.00%     -
SingleSource/Benchmarks/Polybench/linear-algebra/kernels/mvt/mvt 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.453=3> 
79.10%     0.1273     0.2280     -     0.00%     -
SingleSource/Benchmarks/Polybench/linear-algebra/kernels/gemver/gemver 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.478=3> 
48.34%     0.1564     0.2320     -     0.00%     -
SingleSource/Benchmarks/Polybench/linear-algebra/kernels/gemm/gemm 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.367=3> 
46.46%     4.1840     6.1280     -     0.00%     -
MultiSource/Benchmarks/tramp3d-v4/tramp3d-v4 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.355=3> 
44.21%     0.2108     0.3040     -     0.00%     -
SingleSource/Benchmarks/Polybench/linear-algebra/kernels/3mm/3mm 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.65=3> 
24.87%     15.0882     18.8400     -     0.00%     -
SingleSource/Benchmarks/Shootout-C++/hash2 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.46=3> 
19.16%     1.3796     1.6440     -     0.00%     -
SingleSource/Benchmarks/Polybench/linear-algebra/kernels/2mm/2mm 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.150=3> 
14.45%     11.2117     12.8320     -     0.00%     -
SingleSource/Benchmarks/Polybench/linear-algebra/kernels/bicg/bicg 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.255=3> 
14.29%     0.0945     0.1080     -     0.00%     -
MultiSource/Benchmarks/Olden/treeadd/treeadd 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.198=3> 
13.38%     0.0882     0.1000     -     0.00%     -
MultiSource/Benchmarks/TSVC/Symbolics-dbl/Symbolics-dbl 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.135=3> 
11.98%     1.6967     1.9000     -     0.00%     -
MultiSource/Benchmarks/VersaBench/bmm/bmm 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.410=3> 
7.16%     1.3662     1.4640     -     0.00%     -
SingleSource/Benchmarks/Dhrystone/dry 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.153=3> 
4.23%     0.3684     0.3840     -     0.00%     -
MultiSource/Benchmarks/Ptrdist/anagram/anagram 
<http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.128=3> 
3.38%     0.6384     0.6600     -     0.00%     -



Failing Tests (154):
     LeakSanitizer-AddressSanitizer :: 
TestCases/cleanup_in_tsd_destructor.cc
     LeakSanitizer-AddressSanitizer :: TestCases/disabler.cc
     LeakSanitizer-AddressSanitizer :: 
TestCases/disabler_in_tsd_destructor.cc
     LeakSanitizer-AddressSanitizer :: TestCases/ignore_object.cc
     LeakSanitizer-Standalone :: TestCases/cleanup_in_tsd_destructor.cc
     LeakSanitizer-Standalone :: TestCases/disabler.cc
     LeakSanitizer-Standalone :: TestCases/disabler_in_tsd_destructor.cc
     LeakSanitizer-Standalone :: TestCases/ignore_object.cc
     MemorySanitizer :: Linux/fopencookie.cc
     MemorySanitizer :: Linux/getresid.cc
     MemorySanitizer :: Linux/glob.cc
     MemorySanitizer :: Linux/glob_altdirfunc.cc
     MemorySanitizer :: Linux/glob_nomatch.cc
     MemorySanitizer :: Linux/ioctl_sound.cc
     MemorySanitizer :: Linux/mallinfo.cc
     MemorySanitizer :: Linux/obstack.cc
     MemorySanitizer :: Linux/sunrpc.cc
     MemorySanitizer :: Linux/sunrpc_bytes.cc
     MemorySanitizer :: Linux/sunrpc_string.cc
     MemorySanitizer :: Linux/syscalls.cc
     MemorySanitizer :: Linux/tcgetattr.cc
     MemorySanitizer :: Linux/xattr.cc
     MemorySanitizer :: allocator_returns_null.cc
     MemorySanitizer :: backtrace.cc
     MemorySanitizer :: c-strdup.c
     MemorySanitizer :: chained_origin.cc
     MemorySanitizer :: chained_origin_empty_stack.cc
     MemorySanitizer :: chained_origin_limits.cc
     MemorySanitizer :: chained_origin_memcpy.cc
     MemorySanitizer :: chained_origin_with_signals.cc
     MemorySanitizer :: check_mem_is_initialized.cc
     MemorySanitizer :: coverage-levels.cc
     MemorySanitizer :: cxa_atexit.cc
     MemorySanitizer :: death-callback.cc
     MemorySanitizer :: dlerror.cc
     MemorySanitizer :: dso-origin.cc
     MemorySanitizer :: dtls_test.c
     MemorySanitizer :: errno.cc
     MemorySanitizer :: fork.cc
     MemorySanitizer :: ftime.cc
     MemorySanitizer :: getaddrinfo-positive.cc
     MemorySanitizer :: getaddrinfo.cc
     MemorySanitizer :: getc_unlocked.c
     MemorySanitizer :: getline.cc
     MemorySanitizer :: heap-origin.cc
     MemorySanitizer :: iconv.cc
     MemorySanitizer :: if_indextoname.cc
     MemorySanitizer :: ifaddrs.cc
     MemorySanitizer :: initgroups.cc
     MemorySanitizer :: inline.cc
     MemorySanitizer :: insertvalue_origin.cc
     MemorySanitizer :: ioctl.cc
     MemorySanitizer :: ioctl_custom.cc
     MemorySanitizer :: mktime.cc
     MemorySanitizer :: mmap.cc
     MemorySanitizer :: mmap_below_shadow.cc
     MemorySanitizer :: msan_check_mem_is_initialized.cc
     MemorySanitizer :: msan_dump_shadow.cc
     MemorySanitizer :: msan_print_shadow.cc
     MemorySanitizer :: msan_print_shadow2.cc
     MemorySanitizer :: msan_print_shadow3.cc
     MemorySanitizer :: mul_by_const.cc
     MemorySanitizer :: no_sanitize_memory.cc
     MemorySanitizer :: no_sanitize_memory_prop.cc
     MemorySanitizer :: origin-store-long.cc
     MemorySanitizer :: param_tls_limit.cc
     MemorySanitizer :: poison_in_free.cc
     MemorySanitizer :: print_stats.cc
     MemorySanitizer :: pthread_getattr_np_deadlock.cc
     MemorySanitizer :: rand_r.cc
     MemorySanitizer :: readdir64.cc
     MemorySanitizer :: realloc-large-origin.cc
     MemorySanitizer :: realloc-origin.cc
     MemorySanitizer :: report-demangling.cc
     MemorySanitizer :: scandir.cc
     MemorySanitizer :: scandir_null.cc
     MemorySanitizer :: select.cc
     MemorySanitizer :: select_float_origin.cc
     MemorySanitizer :: select_origin.cc
     MemorySanitizer :: setlocale.cc
     MemorySanitizer :: signal_stress_test.cc
     MemorySanitizer :: sigwait.cc
     MemorySanitizer :: sigwaitinfo.cc
     MemorySanitizer :: stack-origin.cc
     MemorySanitizer :: stack-origin2.cc
     MemorySanitizer :: strerror_r-non-gnu.c
     MemorySanitizer :: strlen_of_shadow.cc
     MemorySanitizer :: strxfrm.cc
     MemorySanitizer :: sync_lock_set_and_test.cc
     MemorySanitizer :: textdomain.cc
     MemorySanitizer :: times.cc
     MemorySanitizer :: tls_reuse.cc
     MemorySanitizer :: tsearch.cc
     MemorySanitizer :: tzset.cc
     MemorySanitizer :
1 warning(s) in tests.
: unaligned_read_origin.cc
     MemorySanitizer :: unpoison_string.cc
     MemorySanitizer :: use-after-free.cc
     MemorySanitizer :: vector_cvt.cc
     SanitizerCommon-msan :: Linux/aligned_alloc.c
     SanitizerCommon-msan :: Linux/clock_gettime.c
     SanitizerCommon-msan :: Linux/getpass.cc
     SanitizerCommon-msan :: Linux/getpwnam_r_invalid_user.cc
     SanitizerCommon-msan :: Linux/mlock_test.cc
     SanitizerCommon-msan :: Linux/open_memstream.cc
     SanitizerCommon-msan :: Linux/ptrace.cc
     SanitizerCommon-msan :: Linux/sanitizer_set_death_callback_test.cc
     SanitizerCommon-msan :: Linux/sched_getparam.cc
     SanitizerCommon-msan :: Linux/signal_segv_handler.cc
     SanitizerCommon-msan :: Linux/timerfd.cc
     SanitizerCommon-msan :: Posix/decorate_proc_maps.cc
     SanitizerCommon-msan :: corelimit.cc
     SanitizerCommon-msan :: malloc_hook.cc
     SanitizerCommon-msan :: options-help.cc
     SanitizerCommon-msan :: options-include.cc
     SanitizerCommon-msan :: options-invalid.cc
     SanitizerCommon-msan :: print-stack-trace.cc
     SanitizerCommon-msan :: pthread_mutexattr_get.cc
     SanitizerCommon-msan :: strcasestr.c
     SanitizerCommon-msan :: strcspn.c
     SanitizerCommon-msan :: strpbrk.c
     SanitizerCommon-msan :: strspn.c
     SanitizerCommon-msan :: strstr.c
     UBSan-MSan-x86_64 :: TestCases/Float/cast-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/add-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/div-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/div-zero.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/incdec-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/mul-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/negate-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/no-recover.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/shift.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/sub-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/uadd-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/uincdec-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/umul-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Integer/usub-overflow.cpp
     UBSan-MSan-x86_64 :: TestCases/Misc/Linux/coverage-levels.cc
     UBSan-MSan-x86_64 :: TestCases/Misc/Linux/ubsan_options.cc
     UBSan-MSan-x86_64 :: TestCases/Misc/bool.cpp
     UBSan-MSan-x86_64 :: TestCases/Misc/bounds.cpp
     UBSan-MSan-x86_64 :: TestCases/Misc/deduplication.cpp
     UBSan-MSan-x86_64 :: TestCases/Misc/enum.cpp
     UBSan-MSan-x86_64 :: TestCases/Misc/log-path_test.cc
     UBSan-MSan-x86_64 :: TestCases/Misc/missing_return.cpp
     UBSan-MSan-x86_64 :: TestCases/Misc/nonnull-arg.cpp
     UBSan-MSan-x86_64 :: TestCases/Misc/nonnull.cpp
     UBSan-MSan-x86_64 :: TestCases/Misc/unreachable.cpp
     UBSan-MSan-x86_64 :: TestCases/Misc/vla.c
     UBSan-MSan-x86_64 :: TestCases/TypeCheck/Function/function.cpp
     UBSan-MSan-x86_64 :: TestCases/TypeCheck/misaligned.cpp
     UBSan-MSan-x86_64 :: TestCases/TypeCheck/null.cpp
     UBSan-MSan-x86_64 :: 
TestCases/TypeCheck/vptr-virtual-base-construction.cpp
     UBSan-MSan-x86_64 :: TestCases/TypeCheck/vptr-virtual-base.cpp
     UBSan-MSan-x86_64 :: TestCases/TypeCheck/vptr.cpp

   Expected Passes    : 24015
   Expected Failures  : 138
   Unsupported Tests  : 498
   Unexpected Failures: 154

Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151118/beffdfff/attachment.html>

Daniel Sanders via llvm-dev

2015-Nov-18 16:22 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

I've uploaded the mips/mipsel packages and I'm currently running the
usual tests.

$ sha1sum clang+llvm-3.7.1-rc1-mips*-linux-gnu.tar.xz
78372e1dce17b9e74fbfaa847cc920402aad98ce 
clang+llvm-3.7.1-rc1-mipsel-linux-gnu.tar.xz
acb19bb4a1311b2a0b0b84c55630c1dab1a14364 
clang+llvm-3.7.1-rc1-mips-linux-gnu.tar.xz
> -----Original Message-----
> From: Tom Stellard [mailto:tom at stellard.net]
> Sent: 17 November 2015 03:33
> To: llvm-dev at lists.llvm.org
> Cc: cfe-dev at lists.llvm.org
> Subject: 3.7.1-rc1 has been tagged. Let's begin testing!
> 
> Hi,
> 
> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> reminder, when doing regression testing, use the 3.7.0 release
> as your baseline.
> 
> Thanks,
> Tom

Tom Stellard via llvm-dev

2015-Nov-19 15:13 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

On Wed, Nov 18, 2015 at 11:47:28PM +0800, Ben Pope
wrote:> On Tuesday, November 17, 2015 11:32 AM, Tom Stellard wrote:
> >Hi,
> >
> >I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> >reminder, when doing regression testing, use the 3.7.0 release
> >as your baseline.
> 
> Ubuntu 15.10 x64 uploaded:
> clang+llvm-3.7.1-rc1-x86_64-linux-gnu-ubuntu-15.10.tar.xz
> 
> The regression run seems very good compared to the 3.7.0 run (I have
> a faster SSD now, which may be relevant, I'll rerun the tests
> another time), but PolyBench may have some significant regressions.
> Performance Regressions     18     0
> Performance Improvements     463     0
> Unchanged Tests     1013     1494
> *Total Tests*     *1494*
> 
> 
> Performance Regressions - Execution Time     Δ ▴     Previous
> Current     σ     Δ (B)     σ (B)
> SingleSource/Benchmarks/Polybench/datamining/correlation/correlation
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.193=3>
> 357.01%     0.9829     4.4920     -     0.00%     -
> SingleSource/Benchmarks/Polybench/datamining/covariance/covariance
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.28=3>
> 292.68%     1.1368     4.4640     -     0.00%     -
> SingleSource/Benchmarks/Polybench/linear-algebra/solvers/durbin/durbin
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.284=3>
> 156.05%     0.1406     0.3600     -     0.00%     -
> SingleSource/Benchmarks/Polybench/linear-algebra/kernels/mvt/mvt
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.453=3>
> 79.10%     0.1273     0.2280     -     0.00%     -
> SingleSource/Benchmarks/Polybench/linear-algebra/kernels/gemver/gemver
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.478=3>
> 48.34%     0.1564     0.2320     -     0.00%     -
> SingleSource/Benchmarks/Polybench/linear-algebra/kernels/gemm/gemm
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.367=3>
> 46.46%     4.1840     6.1280     -     0.00%     -
> MultiSource/Benchmarks/tramp3d-v4/tramp3d-v4
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.355=3>
> 44.21%     0.2108     0.3040     -     0.00%     -
> SingleSource/Benchmarks/Polybench/linear-algebra/kernels/3mm/3mm
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.65=3>
> 24.87%     15.0882     18.8400     -     0.00%     -
> SingleSource/Benchmarks/Shootout-C++/hash2
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.46=3>
> 19.16%     1.3796     1.6440     -     0.00%     -
> SingleSource/Benchmarks/Polybench/linear-algebra/kernels/2mm/2mm
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.150=3>
> 14.45%     11.2117     12.8320     -     0.00%     -
> SingleSource/Benchmarks/Polybench/linear-algebra/kernels/bicg/bicg
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.255=3>
> 14.29%     0.0945     0.1080     -     0.00%     -
> MultiSource/Benchmarks/Olden/treeadd/treeadd
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.198=3>
> 13.38%     0.0882     0.1000     -     0.00%     -
> MultiSource/Benchmarks/TSVC/Symbolics-dbl/Symbolics-dbl
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.135=3>
> 11.98%     1.6967     1.9000     -     0.00%     -
> MultiSource/Benchmarks/VersaBench/bmm/bmm
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.410=3>
> 7.16%     1.3662     1.4640     -     0.00%     -
> SingleSource/Benchmarks/Dhrystone/dry
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.153=3>
> 4.23%     0.3684     0.3840     -     0.00%     -
> MultiSource/Benchmarks/Ptrdist/anagram/anagram
> <http://192.168.18.12:8000/db_default/v4/nts/44/graph?test.128=3>
> 3.38%     0.6384     0.6600     -     0.00%     -
> 
> 
> 
Are these tests below new failing tests, or did they fail in 3.7.0 too?

-Tom
> Failing Tests (154):
>     LeakSanitizer-AddressSanitizer ::
> TestCases/cleanup_in_tsd_destructor.cc
>     LeakSanitizer-AddressSanitizer :: TestCases/disabler.cc
>     LeakSanitizer-AddressSanitizer ::
> TestCases/disabler_in_tsd_destructor.cc
>     LeakSanitizer-AddressSanitizer :: TestCases/ignore_object.cc
>     LeakSanitizer-Standalone :: TestCases/cleanup_in_tsd_destructor.cc
>     LeakSanitizer-Standalone :: TestCases/disabler.cc
>     LeakSanitizer-Standalone :: TestCases/disabler_in_tsd_destructor.cc
>     LeakSanitizer-Standalone :: TestCases/ignore_object.cc
>     MemorySanitizer :: Linux/fopencookie.cc
>     MemorySanitizer :: Linux/getresid.cc
>     MemorySanitizer :: Linux/glob.cc
>     MemorySanitizer :: Linux/glob_altdirfunc.cc
>     MemorySanitizer :: Linux/glob_nomatch.cc
>     MemorySanitizer :: Linux/ioctl_sound.cc
>     MemorySanitizer :: Linux/mallinfo.cc
>     MemorySanitizer :: Linux/obstack.cc
>     MemorySanitizer :: Linux/sunrpc.cc
>     MemorySanitizer :: Linux/sunrpc_bytes.cc
>     MemorySanitizer :: Linux/sunrpc_string.cc
>     MemorySanitizer :: Linux/syscalls.cc
>     MemorySanitizer :: Linux/tcgetattr.cc
>     MemorySanitizer :: Linux/xattr.cc
>     MemorySanitizer :: allocator_returns_null.cc
>     MemorySanitizer :: backtrace.cc
>     MemorySanitizer :: c-strdup.c
>     MemorySanitizer :: chained_origin.cc
>     MemorySanitizer :: chained_origin_empty_stack.cc
>     MemorySanitizer :: chained_origin_limits.cc
>     MemorySanitizer :: chained_origin_memcpy.cc
>     MemorySanitizer :: chained_origin_with_signals.cc
>     MemorySanitizer :: check_mem_is_initialized.cc
>     MemorySanitizer :: coverage-levels.cc
>     MemorySanitizer :: cxa_atexit.cc
>     MemorySanitizer :: death-callback.cc
>     MemorySanitizer :: dlerror.cc
>     MemorySanitizer :: dso-origin.cc
>     MemorySanitizer :: dtls_test.c
>     MemorySanitizer :: errno.cc
>     MemorySanitizer :: fork.cc
>     MemorySanitizer :: ftime.cc
>     MemorySanitizer :: getaddrinfo-positive.cc
>     MemorySanitizer :: getaddrinfo.cc
>     MemorySanitizer :: getc_unlocked.c
>     MemorySanitizer :: getline.cc
>     MemorySanitizer :: heap-origin.cc
>     MemorySanitizer :: iconv.cc
>     MemorySanitizer :: if_indextoname.cc
>     MemorySanitizer :: ifaddrs.cc
>     MemorySanitizer :: initgroups.cc
>     MemorySanitizer :: inline.cc
>     MemorySanitizer :: insertvalue_origin.cc
>     MemorySanitizer :: ioctl.cc
>     MemorySanitizer :: ioctl_custom.cc
>     MemorySanitizer :: mktime.cc
>     MemorySanitizer :: mmap.cc
>     MemorySanitizer :: mmap_below_shadow.cc
>     MemorySanitizer :: msan_check_mem_is_initialized.cc
>     MemorySanitizer :: msan_dump_shadow.cc
>     MemorySanitizer :: msan_print_shadow.cc
>     MemorySanitizer :: msan_print_shadow2.cc
>     MemorySanitizer :: msan_print_shadow3.cc
>     MemorySanitizer :: mul_by_const.cc
>     MemorySanitizer :: no_sanitize_memory.cc
>     MemorySanitizer :: no_sanitize_memory_prop.cc
>     MemorySanitizer :: origin-store-long.cc
>     MemorySanitizer :: param_tls_limit.cc
>     MemorySanitizer :: poison_in_free.cc
>     MemorySanitizer :: print_stats.cc
>     MemorySanitizer :: pthread_getattr_np_deadlock.cc
>     MemorySanitizer :: rand_r.cc
>     MemorySanitizer :: readdir64.cc
>     MemorySanitizer :: realloc-large-origin.cc
>     MemorySanitizer :: realloc-origin.cc
>     MemorySanitizer :: report-demangling.cc
>     MemorySanitizer :: scandir.cc
>     MemorySanitizer :: scandir_null.cc
>     MemorySanitizer :: select.cc
>     MemorySanitizer :: select_float_origin.cc
>     MemorySanitizer :: select_origin.cc
>     MemorySanitizer :: setlocale.cc
>     MemorySanitizer :: signal_stress_test.cc
>     MemorySanitizer :: sigwait.cc
>     MemorySanitizer :: sigwaitinfo.cc
>     MemorySanitizer :: stack-origin.cc
>     MemorySanitizer :: stack-origin2.cc
>     MemorySanitizer :: strerror_r-non-gnu.c
>     MemorySanitizer :: strlen_of_shadow.cc
>     MemorySanitizer :: strxfrm.cc
>     MemorySanitizer :: sync_lock_set_and_test.cc
>     MemorySanitizer :: textdomain.cc
>     MemorySanitizer :: times.cc
>     MemorySanitizer :: tls_reuse.cc
>     MemorySanitizer :: tsearch.cc
>     MemorySanitizer :: tzset.cc
>     MemorySanitizer :
> 1 warning(s) in tests.
> : unaligned_read_origin.cc
>     MemorySanitizer :: unpoison_string.cc
>     MemorySanitizer :: use-after-free.cc
>     MemorySanitizer :: vector_cvt.cc
>     SanitizerCommon-msan :: Linux/aligned_alloc.c
>     SanitizerCommon-msan :: Linux/clock_gettime.c
>     SanitizerCommon-msan :: Linux/getpass.cc
>     SanitizerCommon-msan :: Linux/getpwnam_r_invalid_user.cc
>     SanitizerCommon-msan :: Linux/mlock_test.cc
>     SanitizerCommon-msan :: Linux/open_memstream.cc
>     SanitizerCommon-msan :: Linux/ptrace.cc
>     SanitizerCommon-msan :: Linux/sanitizer_set_death_callback_test.cc
>     SanitizerCommon-msan :: Linux/sched_getparam.cc
>     SanitizerCommon-msan :: Linux/signal_segv_handler.cc
>     SanitizerCommon-msan :: Linux/timerfd.cc
>     SanitizerCommon-msan :: Posix/decorate_proc_maps.cc
>     SanitizerCommon-msan :: corelimit.cc
>     SanitizerCommon-msan :: malloc_hook.cc
>     SanitizerCommon-msan :: options-help.cc
>     SanitizerCommon-msan :: options-include.cc
>     SanitizerCommon-msan :: options-invalid.cc
>     SanitizerCommon-msan :: print-stack-trace.cc
>     SanitizerCommon-msan :: pthread_mutexattr_get.cc
>     SanitizerCommon-msan :: strcasestr.c
>     SanitizerCommon-msan :: strcspn.c
>     SanitizerCommon-msan :: strpbrk.c
>     SanitizerCommon-msan :: strspn.c
>     SanitizerCommon-msan :: strstr.c
>     UBSan-MSan-x86_64 :: TestCases/Float/cast-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/add-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/div-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/div-zero.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/incdec-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/mul-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/negate-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/no-recover.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/shift.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/sub-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/uadd-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/uincdec-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/umul-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Integer/usub-overflow.cpp
>     UBSan-MSan-x86_64 :: TestCases/Misc/Linux/coverage-levels.cc
>     UBSan-MSan-x86_64 :: TestCases/Misc/Linux/ubsan_options.cc
>     UBSan-MSan-x86_64 :: TestCases/Misc/bool.cpp
>     UBSan-MSan-x86_64 :: TestCases/Misc/bounds.cpp
>     UBSan-MSan-x86_64 :: TestCases/Misc/deduplication.cpp
>     UBSan-MSan-x86_64 :: TestCases/Misc/enum.cpp
>     UBSan-MSan-x86_64 :: TestCases/Misc/log-path_test.cc
>     UBSan-MSan-x86_64 :: TestCases/Misc/missing_return.cpp
>     UBSan-MSan-x86_64 :: TestCases/Misc/nonnull-arg.cpp
>     UBSan-MSan-x86_64 :: TestCases/Misc/nonnull.cpp
>     UBSan-MSan-x86_64 :: TestCases/Misc/unreachable.cpp
>     UBSan-MSan-x86_64 :: TestCases/Misc/vla.c
>     UBSan-MSan-x86_64 :: TestCases/TypeCheck/Function/function.cpp
>     UBSan-MSan-x86_64 :: TestCases/TypeCheck/misaligned.cpp
>     UBSan-MSan-x86_64 :: TestCases/TypeCheck/null.cpp
>     UBSan-MSan-x86_64 ::
> TestCases/TypeCheck/vptr-virtual-base-construction.cpp
>     UBSan-MSan-x86_64 :: TestCases/TypeCheck/vptr-virtual-base.cpp
>     UBSan-MSan-x86_64 :: TestCases/TypeCheck/vptr.cpp
> 
>   Expected Passes    : 24015
>   Expected Failures  : 138
>   Unsupported Tests  : 498
>   Unexpected Failures: 154
> 
> Ben

Daniel Sanders via llvm-dev

2015-Nov-19 20:01 UTC

head link

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

clang+llvm-3.7.1-rc1-mips-linux-gnu.tar.xz
    2 of 3 complete. All good so far.

clang+llvm-3.7.1-rc1-mipsel-linux-gnu.tar.xz
    All good.

I normally test cross compilation from x86_64 to Mips but the Ubuntu toolchain
doesn't work on my Debian system anymore. Everything failed with:
    libstdc++.so.6: version `GLIBCXX_3.4.21' not found
since my libstdc++ only goes up to GLIBCXX_3.4.20. The OpenSuSE toolchain seems
to work so I've restarted with that. I'll build a proper Debian
toolchain as well just in case.
________________________________________
From: Daniel Sanders
Sent: 18 November 2015 16:22
To: Tom Stellard; llvm-dev at lists.llvm.org
Cc: cfe-dev at lists.llvm.org
Subject: RE: 3.7.1-rc1 has been tagged.  Let's begin testing!

I've uploaded the mips/mipsel packages and I'm currently running the
usual tests.

$ sha1sum clang+llvm-3.7.1-rc1-mips*-linux-gnu.tar.xz
78372e1dce17b9e74fbfaa847cc920402aad98ce 
clang+llvm-3.7.1-rc1-mipsel-linux-gnu.tar.xz
acb19bb4a1311b2a0b0b84c55630c1dab1a14364 
clang+llvm-3.7.1-rc1-mips-linux-gnu.tar.xz
> -----Original Message-----
> From: Tom Stellard [mailto:tom at stellard.net]
> Sent: 17 November 2015 03:33
> To: llvm-dev at lists.llvm.org
> Cc: cfe-dev at lists.llvm.org
> Subject: 3.7.1-rc1 has been tagged. Let's begin testing!
>
> Hi,
>
> I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> reminder, when doing regression testing, use the 3.7.0 release
> as your baseline.
>
> Thanks,
> Tom

Maybe Matching Threads

Search for more maybe matching threads

llvm dev - Nov 2015 - 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] [cfe-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] [cfe-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

[llvm-dev] 3.7.1-rc1 has been tagged. Let's begin testing!

Maybe Matching Threads