public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "irar at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39318] internal compiler error: verify_stmts failed
Date: Sun, 01 Mar 2009 10:34:00 -0000	[thread overview]
Message-ID: <20090301103419.31156.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39318-8911@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from irar at il dot ibm dot com  2009-03-01 10:34 -------
Reduced it a bit more:

      subroutine adw_trajsp (F_u,i0,in,j0,jn)
      implicit none
      real F_u(*)
      integer i0,in,j0,jn
      integer n,i,j
      real*8 xsin(i0:in,j0:jn)
!$omp parallel do private(xsin)
         do j=j0,jn
         do i=i0,in
            xsin(i,j) = sqrt(F_u(n))
         end do
         end do
!$omp end parallel do
      return
      end

on x86_64-suse-linux with 
gfortran -c -fopenmp -fcray-pointer -fexceptions   -O2 -ftree-vectorize.

When we vectorize a function call, we replace the RHS of the stmt with
"something harmless": D.1692_41 = __builtin_sqrtf (pretmp.45_79); is replaced
with D.1692_41 = 0.0;. We don't remove the original stmt from the EH table. The
question is it OK to vectorize function that are in EH table?


-- 

irar at il dot ibm dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenther at suse dot de
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2009-03-01 10:34:19
               date|                            |


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


  parent reply	other threads:[~2009-03-01 10:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 18:03 [Bug fortran/39318] New: " deji_aking at yahoo dot ca
2009-02-27 18:03 ` [Bug fortran/39318] " deji_aking at yahoo dot ca
2009-02-27 18:25 ` dominiq at lps dot ens dot fr
2009-02-27 19:03 ` [Bug middle-end/39318] " dominiq at lps dot ens dot fr
2009-02-27 19:59 ` dominiq at lps dot ens dot fr
2009-02-28 11:18 ` dominiq at lps dot ens dot fr
2009-03-01 10:34 ` irar at il dot ibm dot com [this message]
2009-03-01 10:58 ` rguenther at suse dot de
2009-03-01 11:15 ` irar at il dot ibm dot com
2009-03-01 11:32 ` rguenther at suse dot de
2009-03-01 12:27 ` irar at il dot ibm dot com
2009-03-01 17:51 ` [Bug middle-end/39318] [4.4 Regression] " pinskia at gcc dot gnu dot org
2009-03-02 11:52 ` irar at gcc dot gnu dot org
2009-03-02 13:38 ` rguenth at gcc dot gnu dot 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=20090301103419.31156.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).