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 tree-optimization/34265] Missed optimizations Date: Mon, 03 Dec 2007 14:32:00 -0000 [thread overview] Message-ID: <20071203143206.10123.qmail@sourceware.org> (raw) In-Reply-To: <bug-34265-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #27 from dominiq at lps dot ens dot fr 2007-12-03 14:32 ------- I have had a look at the failure of gfortran.dg/array_1.f90 with patch #5. The following reduced code gives the same failure: ! { dg-do run } ! PR 15553 : the array used to be filled with garbage ! this problem disappeared between 2004-05-20 and 2004-09-15 program arrpack implicit none double precision x(10,10), tmp(6,5) integer i, j x = -1 do i=1,6 do j=1,5 x(i,j) = i+j*10 end do end do tmp(:,:) = x(1:6, 1:5) print '(6F8.2)', tmp end program arrpack With -O3 and patch #5, the output is 11.00 12.00 13.00 14.00 15.00 16.00 -1.00 -1.00 -1.00 -1.00 21.00 22.00 23.00 24.00 25.00 26.00 -1.00 -1.00 -1.00 -1.00 31.00 32.00 33.00 34.00 35.00 36.00 -1.00 -1.00 -1.00 -1.00 instead of 11.00 12.00 13.00 14.00 15.00 16.00 21.00 22.00 23.00 24.00 25.00 26.00 31.00 32.00 33.00 34.00 35.00 36.00 41.00 42.00 43.00 44.00 45.00 46.00 51.00 52.00 53.00 54.00 55.00 56.00 I am amaze that it is the only failure of this kind for the several 1000 tests I have passed! I'll attach the the results of -fdump-tree-optimize for with and without patch #5. I have also looked at the gcc failures. Most of them are missed vectorizations or new ones. So this is already reported. Is *.[0-9][0-9][0-9]t.vect supposed to exist if the vectorization is missed? If yes, this explaina few failures. Concerning the failures with *.[0-9][0-9][0-9]t.cunroll, I see *cunroll1/2, but no cunroll. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34265
next prev parent reply other threads:[~2007-12-03 14:32 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-28 15:27 [Bug tree-optimization/34265] New: " dominiq at lps dot ens dot fr 2007-11-28 15:30 ` [Bug tree-optimization/34265] " dominiq at lps dot ens dot fr 2007-11-28 16:06 ` rguenth at gcc dot gnu dot org 2007-11-28 16:14 ` dominiq at lps dot ens dot fr 2007-11-28 16:18 ` rguenth at gcc dot gnu dot org 2007-11-28 16:34 ` rguenth at gcc dot gnu dot org 2007-11-28 18:18 ` dominiq at lps dot ens dot fr 2007-11-28 18:49 ` dominiq at lps dot ens dot fr 2007-11-28 20:48 ` jb at gcc dot gnu dot org 2007-11-28 21:27 ` burnus at gcc dot gnu dot org 2007-11-28 22:05 ` rguenth at gcc dot gnu dot org 2007-11-28 22:36 ` dominiq at lps dot ens dot fr 2007-11-28 22:49 ` steven at gcc dot gnu dot org 2007-11-28 23:07 ` kargl at gcc dot gnu dot org 2007-11-28 23:18 ` steven at gcc dot gnu dot org 2007-11-28 23:57 ` dominiq at lps dot ens dot fr 2007-11-29 8:06 ` dominiq at lps dot ens dot fr 2007-11-29 10:12 ` rguenth at gcc dot gnu dot org 2007-11-29 10:22 ` dominiq at lps dot ens dot fr 2007-11-29 10:40 ` dominiq at lps dot ens dot fr 2007-11-29 11:01 ` dominiq at lps dot ens dot fr 2007-11-29 11:13 ` rguenther at suse dot de 2007-11-29 11:16 ` dominiq at lps dot ens dot fr 2007-11-29 12:25 ` dominiq at lps dot ens dot fr 2007-11-29 15:49 ` dominiq at lps dot ens dot fr 2007-11-30 21:38 ` ubizjak at gmail dot com 2007-12-03 14:08 ` dominiq at lps dot ens dot fr 2007-12-03 14:32 ` dominiq at lps dot ens dot fr [this message] 2007-12-03 14:34 ` dominiq at lps dot ens dot fr 2007-12-03 14:34 ` dominiq at lps dot ens dot fr 2007-12-03 16:30 ` ubizjak at gmail dot com 2007-12-03 18:59 ` dominiq at lps dot ens dot fr 2007-12-04 6:57 ` irar at il dot ibm dot com 2008-04-23 21:27 ` dominiq at lps dot ens dot fr [not found] <bug-34265-4@http.gcc.gnu.org/bugzilla/> 2011-05-22 12:33 ` dominiq at lps dot ens.fr 2011-09-16 15:53 ` dominiq at lps dot ens.fr 2011-09-17 17:53 ` dominiq at lps dot ens.fr 2011-09-26 9:02 ` rguenth at gcc dot gnu.org
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=20071203143206.10123.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: linkBe 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).