Bug 9916 - [3.2 regression] ICE with noreturn function in ?: statement
Bug#: 9916 Product:  gcc Version: 3.2.2
Host:  Target:  Build: 
Status: RESOLVED Severity: normal Priority: P3
Resolution: FIXED Assigned To: unassigned@gcc.gnu.org Reported By: sobe@ure.cas.cz
Component: c++ Target Milestone: ---
Summary: [3.2 regression] ICE with noreturn function in ?: statement
Keywords:  ice-on-valid-code
Opened: 2003-03-03 12:46
Description:   Last confirmed: Opened: 2003-03-03 12:46 
internal compiler error.

Release:
gcc-3.2.2 compiled with 'make bootstrap'

Environment:
cygwin-w32

------- Comment #1 From Wolfgang Bangerth 2003-03-03 13:42 ------- 
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/9916
Date: Mon, 3 Mar 2003 13:42:06 -0600 (CST)

 The other report I had in mind is PR 7050. It has a similar problem, but 
 also ICEs with 3.3 and mainline.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/

------- Comment #2 From Wolfgang Bangerth 2003-03-03 14:36 ------- 
State-Changed-From-To: open->analyzed
State-Changed-Why: Confirmed. This is the following problem:
    ---------------------
    void no_return () __attribute__((__noreturn__));
    int i
     = (true ? 0 : (no_return(), 0));
    -------------------------------
    It is fixed in 3.3 and 3.4, though, so will probably not
    be fixed for 3.2.x. I keep it open until we decide to
    abandon the 3.2 branch, since it is a regression (didn't
    ICE with 3.0).
    
    W.

------- Comment #3 From Joe Buck 2003-04-25 20:03 ------- 
State-Changed-From-To: analyzed->closed
State-Changed-Why: Fixed for 3.3.