From: Tony Kelman <tony@kelman.net>
To: JonY <10walls@gmail.com>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
Date: Tue, 21 Feb 2017 14:45:00 -0000 [thread overview]
Message-ID: <DM2PR0201MB07991A6F56876CDAA4BC679AA7510@DM2PR0201MB0799.namprd02.prod.outlook.com> (raw)
In-Reply-To: <39ba2d3e-b16e-8d69-d2f0-e6a6e65472ca@gmail.com>
> Do you have a small test case for this instead of running the entire
> test suite? I'm not sure how much time the full test suite takes.
Don't have a small test case, but I do have a big one. I've been
verifying that the patch helps in cross-compiles from opensuse
where it's a lot faster to build a patched gcc (and the test case)
than in cygwin.
Large test case (takes about 15 minutes on my year-old laptop):
curl -L http://llvm.org/releases/3.7.1/llvm-3.7.1.src.tar.xz | tar -xJf -
mkdir -p llvmbuild/bin
cd llvmbuild
echo 'set(CMAKE_C_COMPILER gcc)' > NATIVE.cmake
echo 'set(CMAKE_CXX_COMPILER g++)' >> NATIVE.cmake
cp /usr/i686-w64-mingw32/sys-root/mingw/bin/*.dll bin
cmake ../llvm-3.7.1.src -DCMAKE_SYSTEM_NAME=Windows \
-DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=host \
-DCMAKE_C_COMPILER=i686-w64-mingw32-gcc \
-DCMAKE_CXX_COMPILER=i686-w64-mingw32-g++ \
-DCROSS_TOOLCHAIN_FLAGS_NATIVE=-DCMAKE_TOOLCHAIN_FILE=$PWD/NATIVE.cmake
make -j`nproc` opt
bin/opt.exe -slp-vectorizer \
-S ../llvm-3.7.1.src/test/Transforms/SLPVectorizer/X86/vector.ll
That'll give the following sane LLVM IR output on gcc 4.9, or crash on
unpatched 5+.
; ModuleID = '../llvm-3.7.1.src/test/Transforms/SLPVectorizer/X86/vector.ll'
target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
target triple = "x86_64-apple-macosx10.8.0"
define void @test(<4 x i32> %in, <4 x i32> %in2) {
%k = icmp eq <4 x i32> %in, %in2
ret void
}
> I'll to include the update in the next 5.x release.
Thanks! We're mainly trying to double-check that the patch doesn't
introduce any regressions, cause more problems than it solves.
-Tony
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-02-21 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 4:08 JonY
2016-08-16 9:20 ` Tony Kelman
2016-08-18 0:04 ` JonY
2016-08-18 9:35 ` Tony Kelman
2016-08-18 9:39 ` JonY
2016-08-18 11:51 ` Tony Kelman
2016-08-18 16:15 ` Tony Kelman
2016-08-18 16:37 ` JonY
2016-08-19 19:06 ` Tony Kelman
2016-08-20 2:29 ` JonY
2016-08-23 7:57 ` Tony Kelman
[not found] ` <DM2PR0201MB07999847654538389BC180BAA75E0@DM2PR0201MB0799.namprd02.prod.outlook.com>
2017-02-21 13:28 ` JonY
2017-02-21 14:45 ` Tony Kelman [this message]
2016-08-20 0:35 ` Yaakov Selkowitz
2016-08-20 1:52 ` JonY
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM2PR0201MB07991A6F56876CDAA4BC679AA7510@DM2PR0201MB0799.namprd02.prod.outlook.com \
--to=tony@kelman.net \
--cc=10walls@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).