public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/41082] [4.5 Regression] FAIL: gfortran.fortran-torture/execute/where_2.f90 execution,  -O3 -g with -m64
Date: Tue, 15 Dec 2009 09:58:00 -0000	[thread overview]
Message-ID: <20091215095838.19066.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41082-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from dominiq at lps dot ens dot fr  2009-12-15 09:58 -------
> I can't reproduce it with current mainline on powerpc64-suse-linux. 

I know;)

> Does the good old version gets vectorized?

I don't have any working 4.5 version, but 4.4.2 is working. The differences are

(4.4.2)

where_2.f90:5: note: LOOP VECTORIZED.
where_2.f90:2: note: vectorized 1 loops in function.

(4.5.0)

where_2.f90:11: note: LOOP VECTORIZED.
where_2.f90:11: note: not vectorized: relevant stmt not supported: cond.23_79 =
D.1255_78 > 6;

where_2.f90:11: note: not vectorized: relevant stmt not supported: cond.15_57 =
D.1238_56 == 0;

where_2.f90:11: note: not vectorized: relevant stmt not supported: cond.9_43 =
D.1227_42 < 0;

where_2.f90:5: note: LOOP VECTORIZED.
where_2.f90:2: note: vectorized 2 loops in function.


> Could you please attach vectorizer dump?  If so, could you please attach it as well?

I'll attach the files dumped with -fdump-tree-vect for 4.4 and 4.5.

Note that I make a mistake when looking to my log files: the last working
revision is 149758 and the first failing one is 150041.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41082


  parent reply	other threads:[~2009-12-15  9:58 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-16 10:31 [Bug middle-end/41082] New: " dominiq at lps dot ens dot fr
2009-08-17 11:42 ` [Bug middle-end/41082] " dominiq at lps dot ens dot fr
2009-08-18 20:03 ` dominiq at lps dot ens dot fr
2009-08-19  8:30 ` rguenther at suse dot de
2009-08-25 15:49 ` jsm28 at gcc dot gnu dot org
2009-09-17 20:34 ` dominiq at lps dot ens dot fr
2009-09-17 20:54 ` dominiq at lps dot ens dot fr
2009-09-18  9:01 ` rguenth at gcc dot gnu dot org
2009-12-14 21:10 ` dominiq at lps dot ens dot fr
2009-12-15  8:25 ` irar at il dot ibm dot com
2009-12-15  9:58 ` dominiq at lps dot ens dot fr [this message]
2009-12-15  9:59 ` dominiq at lps dot ens dot fr
2009-12-15 10:00 ` dominiq at lps dot ens dot fr
2009-12-15 10:59 ` irar at il dot ibm dot com
2009-12-15 13:05 ` dominiq at lps dot ens dot fr
2009-12-15 13:07 ` irar at il dot ibm dot com
2009-12-15 13:08 ` irar at il dot ibm dot com
2009-12-15 13:30 ` dominiq at lps dot ens dot fr
2009-12-15 13:35 ` irar at il dot ibm dot com
2009-12-15 14:15 ` dominiq at lps dot ens dot fr
2009-12-15 17:47 ` dominiq at lps dot ens dot fr
2009-12-16  9:22 ` dominiq at lps dot ens dot fr
2009-12-16  9:27 ` dominiq at lps dot ens dot fr
2009-12-16 12:01 ` irar at il dot ibm dot com
2009-12-16 23:36 ` matz at gcc dot gnu dot org
2009-12-20 12:19 ` irar at il dot ibm dot com
2009-12-20 12:46 ` dominiq at lps dot ens dot fr
2009-12-20 13:34 ` rguenth at gcc dot gnu dot org
2009-12-20 13:46 ` irar at il dot ibm dot com
2009-12-20 13:48 ` rguenther at suse dot de
2009-12-20 14:00 ` irar at il dot ibm dot com
2009-12-20 14:19 ` dominiq at lps dot ens dot fr
2009-12-22 11:42 ` irar at il dot ibm dot com
2009-12-22 11:43 ` irar at il dot ibm dot com
2009-12-22 11:44 ` irar at il dot ibm dot com
2009-12-22 16:43 ` dominiq at lps dot ens dot fr
2009-12-22 16:56 ` dominiq at lps dot ens dot fr
2009-12-22 16:59 ` dominiq at lps dot ens dot fr
2009-12-23  7:54 ` irar at il dot ibm dot com
2009-12-23  7:55 ` irar at il dot ibm dot com
2009-12-23  7:55 ` irar at il dot ibm dot com
2009-12-23 14:09 ` dominiq at lps dot ens dot fr
2009-12-23 14:49 ` irar at il dot ibm dot com
2009-12-23 23:34 ` dominiq at lps dot ens dot fr
2010-01-05  9:10 ` irar at il dot ibm dot com
2010-01-10 13:43 ` irar at il dot ibm dot com
2010-01-10 14:22 ` dominiq at lps dot ens dot fr
2010-01-10 14:23 ` dominiq at lps dot ens dot fr
2010-01-10 14:25 ` dominiq at lps dot ens dot fr
2010-04-06 11:24 ` rguenth at gcc dot gnu dot org
2010-05-13 18:04 ` [Bug middle-end/41082] [4.5/4.6 " tkoenig at gcc dot gnu dot org
2010-05-14  9:28 ` [Bug middle-end/41082] [4.5/4.6 Regression] FAIL: gfortran.fortran-torture/execute/where_2.f90 execution, -O3 dominiq at lps dot ens dot fr
2010-07-25 10:20 ` dominiq at lps dot ens dot fr
2010-07-31  9:34 ` rguenth at gcc dot gnu dot org
2010-08-06  7:33 ` dominiq at lps dot ens dot fr

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=20091215095838.19066.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).