public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/10463] -fssa-ccp ICE
Date: Wed, 25 Aug 2004 13:17:00 -0000	[thread overview]
Message-ID: <20040825131714.32368.qmail@sourceware.org> (raw)
In-Reply-To: <20030423120600.10463.davh@diku.dk>


------- Additional Comments From bangerth at dealii dot org  2004-08-25 13:17 -------
Steven, Gaby, you wondered whether this is a regression. Indeed it is. 
Here is a small testcase: 
---------------- 
bool should_exit; 
 
void foo() { 
  int i = 0; 
  while(!should_exit) { 
    int num = 1; 
    if (num) 
      for (int * it; num && it != 0; ) 
        if (*it <= 1) 
          if (i < 1) 
            i = 1; 
  } 
} 
------------------------- 
It compiles with 3.2.3, but ICEs with 3.3.4: 
 
g/x> /home/bangerth/bin/gcc-3.2.3/bin/c++ -c -fssa -fssa-ccp -O2 x.cc 
 
g/x> /home/bangerth/bin/gcc-3.3.4-pre/bin/c++ -c -fssa -fssa-ccp -O2 x.cc 
x.cc: In function `void foo()': 
x.cc:13: internal compiler error: Segmentation fault 
Please submit a full bug report, 
with preprocessed source if appropriate. 
See <URL:http://gcc.gnu.org/bugs.html> for instructions. 
 
Of course the flags were abandoned in 3.4 and later, so it doesn't trigger 
there at all. 
 
Steven, you may want to check whether your patch fixes this problem. 
 
W. 

-- 


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


      parent reply	other threads:[~2004-08-25 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030423120600.10463.davh@diku.dk>
2003-07-08  1:20 ` [Bug optimization/10463] " pinskia at physics dot uc dot edu
2004-08-25 13:15 ` [Bug rtl-optimization/10463] " bangerth at dealii dot org
2004-08-25 13:17 ` bangerth at dealii dot org [this message]

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=20040825131714.32368.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).