From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: gareevroman@gmail.com
Cc: tobias@grosser.es, richard.guenther@gmail.com,
mircea.namolaru@inria.fr,
"Dominique d'Humieres" <dominiq@lps.ens.fr>,
gcc-patches@gcc.gnu.org
Subject: Re: [GSoC] Elimination of CLooG library installation dependency
Date: Sat, 23 Aug 2014 16:48:00 -0000 [thread overview]
Message-ID: <2356BBE4-78D4-4BB9-AB9A-653059E707BA@lps.ens.fr> (raw)
I see two regressions after r214069 on x86_64-apple-darwin13 for both -m32 and -m64:
(1) FAIL: gcc.dg/graphite/vect-pr43423.c scan-tree-dump-times vect "vectorized 2 loops" 1
before I saw
[Book15] f90/bug% grep vectorized vect-pr43423.c.114t.vect
/opt/gcc/p_work/gcc/testsuite/gcc.dg/graphite/vect-pr43423.c:14:17: note: === vect_mark_stmts_to_be_vectorized ===
/opt/gcc/p_work/gcc/testsuite/gcc.dg/graphite/vect-pr43423.c:14:17: note: loop vectorized
/opt/gcc/p_work/gcc/testsuite/gcc.dg/graphite/vect-pr43423.c:12:17: note: === vect_mark_stmts_to_be_vectorized ===
/opt/gcc/p_work/gcc/testsuite/gcc.dg/graphite/vect-pr43423.c:12:17: note: loop vectorized
/opt/gcc/p_work/gcc/testsuite/gcc.dg/graphite/vect-pr43423.c:6:6: note: vectorized 2 loops in function.
after I see
[Book15] f90/bug% grep vectorized vect-pr43423.c.115t.vect /opt/gcc/p_work/gcc/testsuite/gcc.dg/graphite/vect-pr43423.c:14:17: note: not vectorized: not suitable for gather load _55 = a[_56];
/opt/gcc/p_work/gcc/testsuite/gcc.dg/graphite/vect-pr43423.c:12:17: note: not vectorized: not suitable for gather load _36 = a[_37];
/opt/gcc/p_work/gcc/testsuite/gcc.dg/graphite/vect-pr43423.c:6:6: note: vectorized 0 loops in function.
(2) FAIL: gfortran.dg/graphite/pr42393.f90 -O (internal compiler error)
FAIL: gfortran.dg/graphite/pr42393.f90 -O (test for excess errors)
The backtrace is
* thread #1: tid = 0x13bd91f, 0x00007fff8621aca0 libsystem_malloc.dylib`tiny_malloc_from_free_list + 12, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=2, address=0x7fff5bc00ff8)
frame #0: 0x00007fff8621aca0 libsystem_malloc.dylib`tiny_malloc_from_free_list + 12
libsystem_malloc.dylib`tiny_malloc_from_free_list + 12:
-> 0x7fff8621aca0: pushq %rbx
0x7fff8621aca1: pushq %rax
0x7fff8621aca2: movl %edx, %r12d
0x7fff8621aca5: movq %rsi, %r14
(lldb) bt
* thread #1: tid = 0x13bd91f, 0x00007fff8621aca0 libsystem_malloc.dylib`tiny_malloc_from_free_list + 12, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=2, address=0x7fff5bc00ff8)
* frame #0: 0x00007fff8621aca0 libsystem_malloc.dylib`tiny_malloc_from_free_list + 12
frame #1: 0x00007fff8621b3c3 libsystem_malloc.dylib`szone_malloc_should_clear + 320
frame #2: 0x00007fff8621d868 libsystem_malloc.dylib`malloc_zone_malloc + 71
frame #3: 0x00007fff8621e27c libsystem_malloc.dylib`malloc + 42
frame #4: 0x0000000141dbdc79 libgmp.10.dylib`__gmp_default_allocate + 9
frame #5: 0x0000000141dd0148 libgmp.10.dylib`__gmpz_init + 24
frame #6: 0x0000000141c180ef libisl.10.dylib`isl_basic_map_normalize_constraints + 47
frame #7: 0x0000000141c18f04 libisl.10.dylib`isl_basic_map_simplify + 68
frame #8: 0x0000000141c2509b libisl.10.dylib`isl_basic_set_preimage + 619
frame #9: 0x0000000141c4e146 libisl.10.dylib`isl_basic_set_sample_with_cone + 150
frame #10: 0x0000000141c4ea88 libisl.10.dylib`basic_set_sample + 744
frame #11: 0x0000000141c4e849 libisl.10.dylib`basic_set_sample + 169
frame #12: 0x0000000141c09978 libisl.10.dylib`isl_basic_map_is_empty + 136
frame #13: 0x0000000141bb2870 libisl.10.dylib`domain_follows_at_depth + 112
frame #14: 0x0000000141c7cdba libisl.10.dylib`isl_tarjan_components + 154
getting to the ICE take ~19s compared to less than a second before r214069.
Dominique
next reply other threads:[~2014-08-23 16:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 16:48 Dominique d'Humières [this message]
2014-08-24 7:00 ` Roman Gareev
-- strict thread matches above, loose matches on Subject: below --
2014-08-06 15:22 Roman Gareev
2014-08-06 15:48 ` Tobias Grosser
2014-08-07 13:18 ` Roman Gareev
2014-08-07 13:35 ` Tobias Grosser
2014-08-08 13:11 ` Roman Gareev
2014-08-08 13:16 ` Tobias Grosser
2014-08-09 7:42 ` Roman Gareev
2014-08-09 7:52 ` Tobias Grosser
2014-08-09 10:05 ` Roman Gareev
2014-08-11 6:26 ` Tobias Grosser
2014-08-11 7:11 ` Roman Gareev
2014-08-11 7:27 ` Tobias Grosser
2014-08-11 14:20 ` Roman Gareev
2014-08-13 8:07 ` Roman Gareev
2014-08-13 8:56 ` Tobias Grosser
2014-08-13 11:48 ` Roman Gareev
2014-08-13 9:55 ` Richard Biener
2014-08-13 11:49 ` Roman Gareev
2014-08-15 11:13 ` Roman Gareev
2014-08-15 11:45 ` Richard Biener
2014-08-16 5:28 ` Roman Gareev
2014-08-16 10:40 ` Tobias Grosser
2014-08-18 13:00 ` Richard Biener
2014-08-18 15:22 ` Roman Gareev
2014-08-20 3:28 ` Bin.Cheng
2014-08-20 5:24 ` Roman Gareev
2014-08-20 5:47 ` Bin.Cheng
2014-08-21 5:15 ` Bin.Cheng
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=2356BBE4-78D4-4BB9-AB9A-653059E707BA@lps.ens.fr \
--to=dominiq@lps.ens.fr \
--cc=gareevroman@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mircea.namolaru@inria.fr \
--cc=richard.guenther@gmail.com \
--cc=tobias@grosser.es \
/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).