public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/21030] [4.1 Regression] ICE in set_value_range building 176.gcc with -O2
Date: Fri, 22 Apr 2005 22:35:00 -0000	[thread overview]
Message-ID: <20050422223451.6553.qmail@sourceware.org> (raw)
In-Reply-To: <20050414204122.21030.janis@gcc.gnu.org>


------- Additional Comments From kargl at gcc dot gnu dot org  2005-04-22 22:34 -------
This is a shorter version of the Fortran code.  The bug is now
critical to gfortran because almost all Fortran codes contain
nested do loops.

      SUBROUTINE CHER2K(N, C, LDC)

      INTEGER I, J, N, LDC
      COMPLEX C(LDC,*)

      DO 20, J = 1, N
         DO 10, I = 1, J
            C(I,J) = (0.0E+0, 0.0E+0)
   10    CONTINUE
   20 CONTINUE
      END

-- 


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


  parent reply	other threads:[~2005-04-22 22:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 20:41 [Bug tree-optimization/21030] New: " janis at gcc dot gnu dot org
2005-04-14 20:43 ` [Bug tree-optimization/21030] " janis at gcc dot gnu dot org
2005-04-14 20:44 ` [Bug tree-optimization/21030] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-04-14 22:14 ` kazu at cs dot umass dot edu
2005-04-14 23:01 ` kazu at cs dot umass dot edu
2005-04-14 23:02 ` kazu at cs dot umass dot edu
2005-04-19 20:08 ` wanderer at rsu dot ru
2005-04-20 16:43 ` ro at gcc dot gnu dot org
2005-04-22 19:36 ` tobi at gcc dot gnu dot org
2005-04-22 22:35 ` kargl at gcc dot gnu dot org [this message]
2005-04-22 23:03 ` kargl at gcc dot gnu dot org
2005-04-23 10:58 ` toon at moene dot indiv dot nluug dot nl
2005-04-23 13:18 ` dnovillo at gcc dot gnu dot org
2005-04-23 14:13 ` kazu at cs dot umass dot edu
2005-04-23 15:12 ` kargl at gcc dot gnu dot org
2005-04-23 15:15 ` pinskia at gcc dot gnu dot org
2005-04-23 15:46 ` dnovillo at redhat dot com
2005-04-24 14:02 ` kazu at cs dot umass dot edu
2005-04-28 19:34 ` kazu at cs dot umass dot edu
2005-04-29 14:12 ` fxcoudert at gcc dot gnu dot org
2005-04-29 14:17 ` dnovillo at gcc dot gnu dot org
2005-04-29 14:35 ` kazu at cs dot umass dot edu
2005-04-29 14:56 ` kazu at cs dot umass dot edu
2005-04-29 14:59 ` dnovillo at redhat dot com
2005-04-29 16:30 ` kazu at cs dot umass dot edu
2005-04-29 16:32 ` kazu at cs dot umass dot edu
2005-04-29 16:34 ` cvs-commit at gcc dot gnu dot org
2005-04-29 19:57 ` ro at techfak dot uni-bielefeld dot de
2005-04-29 21:11 ` dnovillo at redhat dot com
2005-04-29 21:40 ` dnovillo at redhat dot com
2005-05-02 15:30 ` dnovillo at redhat dot com
2005-05-04 15:05 ` pinskia 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=20050422223451.6553.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).